Forum Discussion
DAX weirdness - nested condition changes behaviour based on output string value
I have the following query for a calculated column, which uses variables set by filtering down tables to a single value. These two variables are then used in a two part conditional statement to set ...
You can't tell from the results which branch of the condition is being returned, because the text will be converted to the same case as the first row to be evaluated. For an example, create 2 tables like
Tmp 1 = { "Ha", "ha" }
Tmp 2 = { "ha", "Ha" }Both rows of the tables will show the same values, with the case depending on which was evaluated first.
So why does this issue go away if I assign values to the variables rather than getting them from the two queries? If it was simply to do with the the first row on which the expression is evaluated, shouldn't that then carry through into the simpler situation where the variables are simply assigned?
From your original post it seemed that the behaviour only changed when you changed the strings which the condition returned ?