Forum Discussion
Helper IClashing Page Filters Different To Visible Arguments
Hi,
After a bit more reading my colleagues found this following article on SQLBI that is very similar to the scenario we came up with, this is a feature known as auto-exist when SUMMARIZECOLUMNS is executed to display a visual.
https://www.sqlbi.com/articles/understanding-dax-auto-exist/
The way to avoid this is to separate the 2 columns into their own dimension tables to avoid auto-exist irreversibly filtering out combinations of values it does not see in its initial context. (Star schema wins again!)
Helper IThank you for the reply,
This would work, however in my working scenario I need to retain the filters on Questions[Type]. Imagine in the scenario above I only wanted to count Question 1 where Category is A or B - Removing filters would also count C which I dont want. I also cannot just assert int he count measure Category = A or B because on different pages of the report I have many different combinations.
I tried just removing filters from Question[QuestionID] but the Question[Type] filter is still being filtered by the selection in Question:
It is as if the filter argument in the measure does not propagate between the 2 page level filters.
Helper IHi,
After a bit more reading my colleagues found this following article on SQLBI that is very similar to the scenario we came up with, this is a feature known as auto-exist when SUMMARIZECOLUMNS is executed to display a visual.
https://www.sqlbi.com/articles/understanding-dax-auto-exist/
The way to avoid this is to separate the 2 columns into their own dimension tables to avoid auto-exist irreversibly filtering out combinations of values it does not see in its initial context. (Star schema wins again!)