Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers!
Enter the sweepstakes now!Preparing for a certification exam? Ask exam experts all your questions on May 15th. Register now.
Help....I'm trying ignore a slicer and have tried using Removefilters, and ALL, but the result is still affected by any selection from the slicer. Is there any suggestion what can be done?
And, is there any way that we can get the dax to ignore slicer but respect the page level filter on the same column?
Solved! Go to Solution.
Hello @AK2025
Thank you for reaching out to the Microsoft Fabric Community Forum
To ignore a slicer but still respect a page-level filter on the same column, you need to isolate the slicer's effect without clearing the entire column context, which ALL('Table'[Service]) and REMOVEFILTERS('Table'[Service]) do they remove all filters, including those from page-level filters.
To solve this, instead of removing all filters, you can selectively preserve the page-level filter context using KEEPFILTERS or by capturing the filter context outside the slicer via a virtual table.
Consider the below DAX:
DEBUG Trial =
CALCULATE(
DISTINCTCOUNT('Table'[Transaction]),
FILTER(
ALL('Table'),
'Table'[Service] IN VALUES('Table'[Service])
)
)
Additionally, If needed, you can consider creating a disconnected slicer table for Service, use that for selection, and write DAX that only uses it conditionally.
If this doesn’t fully meet your needs, could you kindly share a sample of your data and more detailed context? That would help us provide a more accurate solution.
If this response resolves your query, kindly mark it as Accepted Solution to help other community members. A Kudos is also appreciated if you found the response helpful.
Thank You!
Hello @AK2025
Thank you for reaching out to the Microsoft Fabric Community Forum
To ignore a slicer but still respect a page-level filter on the same column, you need to isolate the slicer's effect without clearing the entire column context, which ALL('Table'[Service]) and REMOVEFILTERS('Table'[Service]) do they remove all filters, including those from page-level filters.
To solve this, instead of removing all filters, you can selectively preserve the page-level filter context using KEEPFILTERS or by capturing the filter context outside the slicer via a virtual table.
Consider the below DAX:
DEBUG Trial =
CALCULATE(
DISTINCTCOUNT('Table'[Transaction]),
FILTER(
ALL('Table'),
'Table'[Service] IN VALUES('Table'[Service])
)
)
Additionally, If needed, you can consider creating a disconnected slicer table for Service, use that for selection, and write DAX that only uses it conditionally.
If this doesn’t fully meet your needs, could you kindly share a sample of your data and more detailed context? That would help us provide a more accurate solution.
If this response resolves your query, kindly mark it as Accepted Solution to help other community members. A Kudos is also appreciated if you found the response helpful.
Thank You!
I cannot remove the interactions between the slicer and visual as I will need it for computation of other values to be included in the same visual.
Basically, the computation and slicer comes from the same data table. I have tried both dax (measure dax), but the return results are still filtered by any selection on the slicer on 'Table'[Service]
DEBUG Trial = CALCULATE(DISTINCTCOUNT('Table'[Transaction]),ALL('Table'[Service]))
DEBUG Trial = CALCULATE(DISTINCTCOUNT('Table'[Transaction]),REMOVEFILTERS('Table'[Service]))
Hi @AK2025 simple way is you can use the Edit Interactions between slicer and the visual, thus slicer wont affect the visual and visual will be filtered when page level filter is selected
Hi,
Without seeing your sample pbix file, I am not sure how your semantic model looks like, but I guess your model includes sort_order column for the specific column.
I tried to create a sample pbix file like below, and please check the below picture and the attched pbix file.
expected result measure: =
CALCULATE (
SUM ( sales[sales] ),
REMOVEFILTERS ( reason_slicer[reason], reason_slicer[reason_sort_order] )
)
If this post helps, then please consider accepting it as the solution to help other members find it faster, and give a big thumbs up.
Check out the April 2025 Power BI update to learn about new features.
Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.
User | Count |
---|---|
19 | |
13 | |
11 | |
10 | |
9 |