Forum Discussion
ALL() function ignored / inconsistent functionality when also using report level filter
Hi,
I got a response from Microsoft to my ticket and wanted to share the result. This did fix the problem as per screenshot below. I'm not sure why there is a difference between PBI and PowerPivot results, but I'm grateful to have something to work with. It is not clear whether the Power BI support team considers this a bug or not as they refer more to "problem" and "workaround". I was under the impression everything could be done from a flat table in PBI if only one source being used, but it's not much admin to add to link up at least. Thanks all for the input.
Microsoft support response
Use the ALL function on the dimension attribute instead of the column in the fact table, and use the slicer on the dimension attribute, this seems to workaround the problem.
Am waiting on Microsoft Power BI team to respond... For interest - I built the same test in PowerPivot and found that it worked perfectly. Screenshot below
Which is a little concerning for Power BI. It was pretty obvious to me that something didn't seem right, but what if there are other DAX engine issues which seem more subtle? I'm sure Microsoft will help sort it out quickly though.
Thanks for pointing out this issue and raising with Microsoft!
I played around with your example and created a simple example of my own, and the behaviour seems to be the same whether the filters are applied through slicers or Report Level filters.
The behaviour seems to be:
- For the set of columns that have 'slicers' (or I guess any filter) applied (i.e. the Columns for which ISFILTERED( Column ) = TRUE ), cross-filtering is applied among those columns.
- This results in a reduced list of values per filtered column.
- When the DAX expression is evaluated, ALL(...) correctly clears the filters on columns specified, but the cross-filtered values for the other columns are retained!!!
For example, when you filtered Date ID = 01, 02, 03 and StartDay = Mon, cross-filtering reduced Date ID down to just 01.
Then the DAX expression cleared the filter on StartDay, but Date ID was left filtered to just 01, resulting in a row count of 3.
Of course this is all incorrect behaviour. Hopefully fixed soon!
Yep! Curious to see what they say about this?
Thanks Owen and Sean for also looking into this, much appreciated! I did raise a ticket with Microsoft through the ticket system on the website on Monday afternoon SA Time ( Monday morning US time). As a Pro subscriber, they said I'd hear back from them in one business day... I've heard nothing back from them. Anybody know how I can raise the urgency with them on this? As an "engine" issue, this is causing patently incorrect results on my report, and I'm sure may other people's reports too, but perhaps they are just not noticing it because it is less obvious! So I perceive this to be fairly serious and thought I'd have heard back from them by now.
For anybody Microsoft on this forum, my ticket number is 116101014778110.
As an aside, Icouldn't find any send a frown on the desktop version or online version, and the "smile" button just gives you an option to "get help" which takes you to https://powerbi.microsoft.com/en-us/support/ which is where I logged the ticket...
