Forum Discussion

bswylie's avatar
bswylie
Helper I
9 years ago
Solved

ALL() function ignored / inconsistent functionality when also using report level filter

While working on an analysis report we came across (what seems to be) an issue in Power BI, and are not sure if this is a bug or a misunderstanding on our part. In summary, a measure we have created ...
Need Help
  • bswylie's avatar
    bswylie
    9 years ago

    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.

     

     

Anonymous's avatar
Anonymous
Not applicable
3 years ago

Hi folks,

 

I am running into the same issue. Is there a solution to resolve this wihtout breaking out all columns that I potentially ever want to filter by into separate dimension tables? I mean there has to be a way to at least ditch all the filter context in a measure and then just reapply only the slicer that I want to keep, right?

 

Background:

I have a table with some 300 columns in my data model that users want to build reports for and there is absolutely zero chance I am breaking this out into dimension tables. IMHO is no proper version control or automation / programmation feature built into MS so I just won't do it. For the exat same reason, there are other voices that consider star schema not fit for many modern ways of working as explained in Why star schema is set up for failure and in Should auto exist and sort by column implementation be changed?

 

Cheers, aabtra