Cartesian product in DAX (TREATAS) by using 0 values in combination with field parameters

lbendlin v-kpoloju-msft 

Unfortunately, Microsoft Support was unable to provide a specific solution or workaround. The case was classified as a development scenario, which the Break/Fix team does not cover, and I was therefore advised to reach out to a Microsoft Partner (which isn't a viable solution for me).

I understand that this limitation is achieved by the generated DAX statement. I may be wrong, but in my opinion, the generated DAX statement itself is a bug and is not comprehensible.

In the meantime, I performed additional analysis and discovered that the issue occurs not only when using field parameters, but also when working with individual / explicit columns. The behaviour appears when changing the aggregation of numeric columns from “Sum” to “Don’t summarize”.

This gave me the idea of creating explicit measures (aligned with best practices). When referencing these measures within the field parameters, the generated DAX code becomes more efficient, and I no longer encounter the previous limitations.