Forum Discussion
Measure not calculating value when there is no data in selected columns, despite filter modifiers
Super UserThe very idea of a Power BI data model relies on rigid single column joins. Everything influences everything else (as per the arrow direction). The best you can get is a left outer join (ish).
Your usage scenario calls for cross joins. Those are not supported (and frankly not desired) in the Power BI data model paradigm. Hence the need for disconnected tables.
Thank you very much for the replies!
I understand that much, but I was confused as to why a function like ALL() wouldn't work in my scenario, but upon reviewing the documentation I found the following:
"The normal behavior for DAX expressions containing the ALL() function is that any filters applied will be ignored. However, there are some scenarios where this is not the case because of auto-exist, a DAX technology that optimizes filtering in order to reduce the amount of processing required for certain DAX queries. An example where auto-exist and ALL() provide unexpected results is when filtering on two or more columns of the same table (like when using slicers), and there is a measure on that same table that uses ALL(). In this case, auto-exist will merge the multiple filters into one and will only filter on existing combinations of values. Because of this merge, the measure will be calculated on the existing combinations of values and the result will be based on filtered values instead of all values as expected."
I am going to try to understand this and see possible ways to circumnavigate the problem.
Still seems to me like a pretty important limitation.
Thanks again for your replies!
- lbendlin
I am going to try to understand this and see possible ways to circumnavigate the problem.That's what we call "fighting the API". Don't try to make Power BI do things it was not designed to do. Embrace the concept of Power BI. If you cannot do that, use a different tool with a design paradigm that matches your intentions.