Forum Discussion
Power BI Import changes text case when only letter casing differs
This is expected behaviour. While Power Query is case sensitive, DAX is not. The exact case which is stored depends on the order the data is loaded, e.g. if "100ML" is loaded before "100ml" then all values will be stored as "100ML". If no explicit order is specified in the query then the ordering could potentially change each time the data is loaded, depending on the behaviour of the underlying DB engine.
Thank you very much for your explanation.
So, if I understand correctly, this means there is currently no way to preserve the original letter casing (for example, "100mL" and "100ML") when using Import mode in Power BI, and this behavior is expected.
Although this is not the answer I was hoping for, I appreciate your clear explanation. Thank you for taking the time to help me.
You understand correctly, there is no way to do it.
That is expected behavior. The VertiPaq engine treats text values as case-insensitive for storage and dictionary encoding, so it retains only the first encountered instance regardless of letter casing. While there are workarounds to preserve or distinguish different casing, they typically introduce additional processing overhead and can become quite slow when working with large tables. Try this: https://youtu.be/zucfRfE2MEA?si=jUiiWtiXVar15Ypu
