Data Modeling Uppercase and Lowercase issues

[mancs]

Hello,

I'm pulling data from a MYSQL server and among the data that I have there several entries which have similar input however they differ from each other by having some of the letters in their composition UPPERCASE or LOWERCASE, the reasoning behind this is beyond me since I didn't create the database. Regardless, I need to accept all of the entries, however, whenever I apply my modifications to the query editor it transforms part of the entries from LOWERCASE to UPPERCASE values which create duplicates, which in turn doesn't allow me to have a table with unique values. There several examples of this disturbance, the screens bellow show once such case. Any ideea on how to retain the values unchanged from Query Editor to Data View?Query Editor

Data View

[JVidal]

This needs to be addressed ASAP. It's been already too long with this issue.

[dinkumdata]

@Admin Can you please respond to let us know if this is going to be addressed as a bug by the Power BI team. As mentioned by everyone on this thread, this automatic conversion of Uppercae to Lowercase and vice versa depending on which case occure first in the data is creating havoc with fields that are being used a ID/key columns for relationships and consequently joins which therefore creates inaccuracies in the data. For a data visualisation tool of Power BI's calibre this should not be an issue and furthermore for an issue that has been raised just over 4 years ago this should surely have been addressed by the Power BI team by now?! Please can you or someone from the Power BI team come back to us with steps to getting this issue resolved.

[Anonymous]

Just came across this issue today. In my case the label is not used as an identifier but anyhow is hard to explain to a client that the report is ok even when it displays the information diferently than what he inserted...

Please consider solving this issue (or is it a bug??)

[Anonymous]

A workaround for is to use the:

lower(FIELDNAME) as "fieldname" 

function in the *Source SQL*  in the which will consistently deliver it to Power BI lowercased.

upper(fieldname) would also work, as long as you're consistent.

[Anonymous]

What does the status "Delivered" means? I dont think this is fixed...

[Anonymous]

"delivered" meaning "transfer the data to..."  

[Anonymous]

@Anonymous does that mean this issue was delivered to the PBI team for fixing? 

[graxxon]

This bug (or feature) is not requested. The Power BI application should be also case sensitive. We would like to show the difference between the case sensitive values, but in this application these values are hidden and the result value is altered (displaying false results). Please could you add an option to change the text to case sensitive? Thank you in advance for your help and support.

[newbie318]

Any resolution to this problem? We have a data model where the unique identifiers may use the same sequence of letters (and numbers) but are case sensitive? Please help.

[PAPutzback2]

Until this is fixed, I'd suggest wrangling the data outside of PowerBI and creating flags that power BI can use.