Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more
Hi Community, I need your help to understand why in the table view I see different values than in Power Query and in the data source.
As a result the number of distinct values for the Order State field is lower in Table View than in Power Query.
Please note that I have the latest version of Power BI Desktop and refreshed the data in both views.
Thanks for your help,
Carmen
Solved! Go to Solution.
@CarmenTurnagiu Because the first obvious feature that you want in a data analytics tool is for the tool to immediately munge your data, Power BI's semantic model is stupidly case insensitive in that the first instance of a word is the casing that will be adopted for all instances of that word. It's the absolute dumbest thing imaginable that Power BI does not allow you to turn off this "feature" (because the tabular data model doesn't have to be implemented this way). Here's a video I made on it:
@CarmenTurnagiu Because the first obvious feature that you want in a data analytics tool is for the tool to immediately munge your data, Power BI's semantic model is stupidly case insensitive in that the first instance of a word is the casing that will be adopted for all instances of that word. It's the absolute dumbest thing imaginable that Power BI does not allow you to turn off this "feature" (because the tabular data model doesn't have to be implemented this way). Here's a video I made on it:
Many thanks for your reply @Greg_Deckler Greg. It is confusing and difficult for me to understand why power query would be case sensitive but power bi engine not.
@CarmenTurnagiu Incredibly poor design.
Check out the April 2025 Power BI update to learn about new features.
Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.
User | Count |
---|---|
100 | |
63 | |
45 | |
36 | |
35 |