We are experiencing an issue in Power BI where text data behaves differently between the report view and exported files.
In the Power BI report, the data displays correctly with the original case preserved (case-sensitive as per the source). However, when exporting the same data to Excel, the text values are automatically converted to lowercase.
We validated the source data format after following the recommended troubleshooting steps, and the casing is correct at the source level. Despite this, the issue persists only during export.
As suggested by the product team, we also tried exporting the report data as a .CSV file instead of a standard Excel file. Unfortunately, the problem still occurs, and the exported data continues to appear in lowercase.
This inconsistency between report visualization and export behavior can lead to data quality and reporting concerns, especially for use cases where text casing is critical (for example, codes, identifiers, or business-specific naming conventions).
Request:
We request an enhancement or fix to ensure that exported data (Excel or CSV) preserves the original text casing exactly as displayed in the Power BI report and source data. Additionally, improved transparency or documentation around export transformations would be helpful.
Recent ideas
Auto-generate INSERT VALUES scripts for configuration data migration across environments
Hi Fabric Team, I would like to suggest a feature that could significantly simplify deployment and environment promotion activities. Today, when configuration tables contain reference or applicatio...todigen2 hours agoRegular VisitorNew9Views1like0CommentsAllow Non-Breaking Schema Changes in Fabric CI/CD Deployments for Data Warehouse Objects
Hi, currently, Microsoft Fabric deployment pipelines can fail when a Data Warehouse deployment contains schema changes such as adding, removing, renaming, or modifying columns in existing tables. I...todigen3 hours agoRegular VisitorNew8Views0likes0CommentsAllow Non-Breaking Schema Changes in Fabric CI/CD Deployments for Data Warehouse Objects
Hi, currently, Microsoft Fabric deployment pipelines can fail when a Data Warehouse deployment contains schema changes such as adding, removing, renaming, or modifying columns in existing tables. I...todigen3 hours agoRegular VisitorNew18Views1like0Comments