Page Level filter

[Omega]

Hi, 

How to ignore page level filter when, ALL, VALUES, REMOVEFILTERS, KEEPFILTERS, TREATAS, ALLEXCEPT, TREATEAS, and ALLSELECTED can't ignore it?!

[v-lgarikapat · Accepted solution]

Hi @Omega ,

Thanks for reaching out to the Microsoft fabric community forum.

@sevenhills , @Ilgar_Zarbali 

Thanks for your prompt response

@Omega 

Workaround implemented:
To solve this, I’ve used a disconnected slicer table

I have uploaded the PBIX file here for your reference.

If you’re still experiencing any issues, please feel free to let us know  we’ll be happy to assist you further.

Looking forward to your response.

If this post helped resolve your issue, please consider marking it as the Accepted Solution. Doing so not only acknowledges the support provided but also helps other community members find relevant solutions more easily.

We appreciate your engagement and thank you for being an active part of the community.

Best regards,
LakshmiNarayana.

[v-lgarikapat]

Hi @Omega ,

If your issue has been resolved, please consider marking the most helpful reply as the accepted solution. This helps other community members who may encounter the same issue to find answers more efficiently.

If you're still facing challenges, feel free to let us know we’ll be glad to assist you further.

Looking forward to your response.

Best regards,
LakshmiNarayana.

[sevenhills]

I have used page filters and used ALL, it worked for me. 

Not sure these links will help:

https://www.sqlbi.com/articles/understanding-dax-auto-exist/

https://forum.enterprisedna.co/t/delinking-page-filters-on-few-visuals/7271/4

Could you share the model diagram, page filters, dax that you tried... sometimes, we may have to use all(dimtable) too in combination of all(fact table). 

[Ilgar_Zarbali]

If ALL, REMOVEFILTERS, VALUES, KEEPFILTERS, ALLEXCEPT, TREATAS, and ALLSELECTED can't help you ignore a Page-Level filter, then you're facing a scenario where DAX cannot override the page-level filter because it is already being enforced at the visualization layer before DAX is evaluated.

Page-level filters are enforced by the Power BI engine before your DAX code executes. This means DAX can't override or "see beyond" them — not even with functions like ALL or REMOVEFILTERS.

Solution 1: Move the page-level filter to a slicer (visual-level filtering)

If your goal is to exclude a certain visual from being affected:

1. Remove the Page-level filter, and instead use a slicer (which gives more control).
2. Then, for visuals that should ignore the slicer, go to the Visual Interactions settings:

• Click on the slicer ➝ Format tab ➝ Edit Interactions
• Set unwanted visuals to "None" so they ignore the slicer.

Solution 2. Use a Disconnected Table (if you want selective control)
You can create a disconnected filter table that mimics the original column:

DisconnectedDate = DISTINCT('Calendar'[Date])

Then, create a measure using TREATAS():

Custom Measure =
CALCULATE(
    [Your Measure],
    TREATAS(VALUES('DisconnectedDate'[Date]), 'Calendar'[Date])
)

This bypasses the regular relationship-based filtering — and thus ignores any page-level filters applied to Calendar[Date].


If you found the above information helpful, I’d appreciate it if you could give us a Kudos and mark the response as the Accepted Solution.