Model Joins on Strings Error

The second one is related and I have read that while trying to work out what is happening.  It's just another workaround to a broken model of treating all string values as case-insensitve.  Users are left to try and find workarounds to meet their scenario (read the comments on that post to see what this behaviour is doing to URL's etc).

This is an issue caused by DAX treating strings as case-insensitive values, rather than just leaving them alone.

The stack overflow post doesn't have any offered solution.

As I say there is a workaround of creating a surrogate key, but that means modifying the data warehouse models and not going to be a simple job.  Another work around for my scenario is to create a binary rendition of the string in M using Text.ToBinary() and to do that on both sides of the join before the tables move into the model.

However, this fundementally is a bug that should be fixed in the tool, rather than being left to the community to find workarounds, that meet some but not all scenarios.