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 name and description to Item Schedule
A Fabric item can now have up to 20 schedules attached to it. These schedules can have different purposes, let's say one is for nightly runs and another one is for runs during working hours. ...frithjof_v7 minutes agoCommunity ChampionUnder Review3.4KViews21likes5Comments- axserv53 minutes agoNew MemberPlanned9.1KViews139likes15Comments
Monitor Hub (Preview) - Keyword Search Should Search Across All Pages
In the Monitor Hub (Preview) Job Runs experience, the "Filter by keyword" search currently searches only the items loaded on the current page. As documented, if a matching item exists on a later pag...swetha123 hours agoMicrosoft EmployeeNew38Views13likes0Comments