Appreciate case sensitivity in Power Query
As explained before, Power Query is case-sensitive. Case sensitivity is not just about the Power Query syntax; string data types in opposite cases are not equal in Power Query. So it is essential to pay attention to character cases when working with string data. When we mash up data from different sources, we often have GUIDs as key columns (either a primary or a foreign key). We get incorrect results if we compare the GUID values with different cases. For instance, in Power Query, the following values are not equal:
C54FF8C6-4E51-E711-80D4-00155D38270Cc54ff8c6-4e51-e711-80d4-00155d38270c
Therefore, if we merge two tables joining the key columns, we get weird results. It is also the case if we load the data into the data model and create a relationship between two tables with key columns in different character cases. The solution is simple; we only need to keep both key columns in the same character case using either...
