Forum Discussion
Case Sensitivity
I need/want to maintain Case Sensitivity when creating reports.
It seems that PowerBi now changes the case on my excel data source as seen on this table visual
How can I fix this?
Power Query is case-sensitive, that's why you can add an index there to protect your sensistivity since Power BI is case-insensitive.
8 Replies
Hello! The main engine of Power BI is case-insensitive. However, you can create a workaround for this by creating an index for the different case values in Power Query because case-sensitivity is recognized there. Here is a blog that should help explain in more detail: Letter case-sensitivity in DAX, Power BI and Analysis Services - SQLBI
I thought at one time, case sensitivity was not auto-corrected in PowerBi . Did this change or perhaps I am thinking of relationships between tables or some other element.
Power Query is case-sensitive, that's why you can add an index there to protect your sensistivity since Power BI is case-insensitive.
PaulPalkowski Hey,
Kindly refer below webpage.Power BI: How To Transform Data To Uppercase (quicklylearnpowerbi.com)
or
you can go power query
select column => transform => you can select "capitalize each word"
to get all word as same in your excel.Thanks
Harish
Did I answer your question? Mark my post as a solution!no, i want to keep the data as entered... What I shared was only an example. What I have is product assignment naming conventions such as 1524E-PP and 1524E-pp where the PP means it has been inspected and the pp means it has not. The are many variations such as e1487-c is aprototype but e1487-C is and approved part. The letter's case in the hundreds of part numbers represents various stages.
Thank You!
You're welcome!
This is a huge problem for the architecture/engineering/construction community (BIM/VDC). We want to use the unique IDs of the IFC file format (IFC GUID) for 3D buildings and their data, but it's a case sensitive key.
Example: 2F$L$p5YXH0f$q71wYJpYvAs a result, what should be a simple logical connection becomes a data nightmare.
You can vote on this issue here to encourage Microsoft to allow us the flexibility to have this precision with our data: https://community.fabric.microsoft.com/t5/Fabric-Ideas/Case-sensitive-insensitive-option-in-Power-BI/idi-p/4528490
