Forum Discussion
Helper ICasing on text fields doesn't always match the data
Helper IThanks for the response Venessa,
Unfortunately, using all upper or lower isn't going to be an option. It's a customer-facing report, and the specific capitalizations are done the way they are for a reason.
I'm using the "Table" visual.
As far as the power query code, are you referring to the code from the SQL statement? I can't share it for confidentiality reasons, but it's quite dirt simple. The columns are being pulled directly from the tables, nothing fancy, no case statements or functions being applied. Like I said, both in the power query editor and in the SQL Server Management Studio environment, I can see that the text casing is correct. Only on the "table" visual is it coming through with some inaccurate casing.
Community Championi assumed they were all a specific case. I mean the power query code from the advanced editor, you can block confidential information.
sounds like a very odd problem, its very hard to figure out the issue if you can't share more details.
Is the problem the same in other visuals such as the matrix, or even a card or other text visuals?
- pbi_106
Hey Venessa,
I'm able to reproduce the issue using a matrix or card visualization as well. I added these visualizations and added a couple of columns, including the problem column, but left everything else on these visualizations at their defaults. Still very confused as to what is happening with the casing on these values between seeing them properly formatted in the Power Query editor and seeing the casing inconsistently formatted through visualizations on the report.