Forum Discussion
Casing on text fields doesn't always match the data
A few more details about the report that I'm hoping could help to give me another lead in troubleshooting this weird issue:
1. The column that I added is a free-text field from one of our apps. It allows users to enter comments about the location of where a particular customer can be found within a building.
2. There are plenty of instances in which the same value, such as "2nd floor" or "Media Center" can be populated for multiple different customers. These might have different casing depending on how the user entered it (for example, "media center", "Media Center", "media Center" or "MEDIA CENTER").
3. In my Power BI report, I can filter onto a specific customer that has "Media Center" as the value coming from the database as well as the Power BI Query Editor, but the visualization shows "MEDIA CENTER" instead.
4. Basically, the instances in which this issue is occurring are those cases in which the same value has also been entered for another customer, but with different casing. It seems like Power BI, rather than using the precise casing of the value associated with the specific customer, is often using the casing of a different customer's otherwise identical location comment value.
Hopefully this makes sense. Any way to force Power BI to use the exact casing for that customer's location value?