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
Add Automated Pre-Upgrade Compatibility Assessment for Fabric Spark Runtimes
Microsoft Fabric should provide an automated compatibility assessment before a workspace, Environment, notebook, or Spark Job Definition is upgraded to a newer Fabric Runtime. Spark runtime upgra...mourakshit29 minutes agoNew MemberNew2Views0likes0CommentsSupport Creator-Independent Managed Identity and Ownership Transfer for Fabric Operations Agents
Microsoft Fabric Operations Agents should support an enterprise identity and ownership model that is independent of the individual user who originally created the agent. Today, an Operations Agent r...mourakshit31 minutes agoNew MemberNew2Views0likes0CommentsAdd Centralized Health, Freshness Monitoring, and Alerts for OneLake Shortcuts
Microsoft Fabric should provide a centralized health-monitoring experience for OneLake Shortcuts across workspaces and data sources. As organizations adopt OneLake Shortcuts at enterprise scale, hun...mourakshit34 minutes agoNew MemberNew2Views0likes0CommentsAdd Schema Compatibility Policies and Breaking-Change Detection to Fabric Event Schema Registry
Fabric Event Schema Registry should support configurable schema compatibility policies so teams can safely evolve event contracts without breaking downstream Eventstreams, Eventhouse ingestion, appli...mourakshit36 minutes agoNew MemberNew2Views0likes0CommentsAdd Dry-Run Simulation and Historical Event Replay for Fabric Activator Rules
Fabric Activator should provide a dry-run simulation mode that allows developers to test rules against historical or sample event data without executing real downstream actions. Activator rules can ...mourakshit38 minutes agoNew MemberNew2Views0likes0Comments