DAX: Ignore One Slicer but Keep Every Other Filter

To make a DAX measure ignore one slicer but keep every other filter,
remove the filter from the slicer’s exact column inside
CALCULATE:

Sales Ignoring Color =
CALCULATE (
    [Sales Amount],
    REMOVEFILTERS ( Product[Color] )
)

This clears Color while keeping Date, Customer, Region, Product
Category, Brand, and other filters.

The scope is the whole problem. Remove too broad a table and the
measure ignores more than the user intended.

Start with the
narrowest possible filter removal

Suppose the report has slicers for:

• Date
• Region
• Product Category
• Product Color

The requirement is for one benchmark line that ignores Color
only.

Use:

Benchmark Sales =
CALCULATE (
    [Sales Amount],
    REMOVEFILTERS ( Product[Color] )
)

Avoid:

-- Too broad when Category and Brand should remain active
Benchmark Sales =
CALCULATE (
    [Sales Amount],
    REMOVEFILTERS ( Product )
)

Table-level removal clears every Product column, including filters
that arrived indirectly through related Product attributes.

Confirm which
column the slicer actually uses

A report can contain similar fields:

• Product[Color]
• Color Selector[Color]
• Sales[Color]

Removing Product[Color] does nothing to a slicer built
from a disconnected Color Selector table.

Select the slicer and inspect its field. Then add:

Debug Visible Colors =
CONCATENATEX (
    VALUES ( Product[Color] ),
    Product[Color],
    ", "
)

If this measure does not change with the slicer, the slicer is not
directly filtering Product[Color].

A normal connected slicer

For a connected Product dimension:

Sales Amount =
SUM ( Sales[SalesAmount] )

Sales Ignoring Color =
CALCULATE (
    [Sales Amount],
    REMOVEFILTERS ( Product[Color] )
)

Test:

1. Select one color.
2. Select multiple colors.
3. Clear the slicer.
4. Change Category.
5. Change Date.

The base measure should respond to every selection. The benchmark
should ignore Color but still respond to Category and Date.

A
disconnected slicer requires a different pattern

Disconnected slicers do not filter the model by themselves. A measure
reads and applies the selection, often with TREATAS:

Sales for Selected Color =
CALCULATE (
    [Sales Amount],
    TREATAS (
        VALUES ( 'Color Selector'[Color] ),
        Product[Color]
    )
)

To ignore that selector for another measure, simply do not apply its
TREATAS:

Sales Ignoring Color Selector =
[Sales Amount]

Adding REMOVEFILTERS ( 'Color Selector' ) may be useful
when a nested measure reads the selector, but clearing a disconnected
table does not remove a Product filter that was already applied
elsewhere.

Trace where the virtual filter enters the dependency chain.

Keep a
parent filter while ignoring a child filter

Suppose Category and Color both come from Product. You want to keep
Category but ignore Color:

Category Sales Ignoring Color =
CALCULATE (
    [Sales Amount],
    REMOVEFILTERS ( Product[Color] )
)

This is preferable to:

CALCULATE (
    [Sales Amount],
    ALLEXCEPT ( Product, Product[Category] )
)

ALLEXCEPT clears every other Product column—not just
Color. That may remove Brand, Subcategory, Product, or another filter
added later.

Name the one filter to remove when the requirement names one
filter.

Ignore the slicer
for one visual without DAX

If the requirement is purely presentational—one chart should not
react to the slicer—Power BI visual interactions may be the cleaner
solution.

Select the slicer, open Format → Edit interactions,
and choose None for the target visual.

Microsoft’s
slicer guidance explains that report authors can control which
visuals a slicer affects.

Use visual interactions when:

• the entire visual should ignore the slicer;
• every measure in that visual should behave the same way; and
• the exception is a report-layout rule.

Use DAX when:

• one measure should ignore the slicer while another responds;
• the logic must travel with the measure; or
• the exception is part of the business definition.

Ignore
one slicer but keep another slicer on the same table

This works when the slicers target separate columns:

Sales Ignoring Brand =
CALCULATE (
    [Sales Amount],
    REMOVEFILTERS ( Product[Brand] )
)

A Category slicer still filters Product. However, Power BI’s
automatic combination of filters from the same table can create subtle
behavior in some models. Test the exact combinations and consider
whether separate dimensions better represent the business entities.

Do not clear the entire Product table and then try to reconstruct
every filter manually. That pattern is fragile when the model gains new
attributes.

Ignore a date
slicer but keep a date grouping

This is a special case. If the slicer and visual axis use the same
Date column, removing the slicer filter also removes the row’s date
filter:

CALCULATE (
    [Sales Amount],
    REMOVEFILTERS ( 'Date'[Date] )
)

Every row can then show the same total.

You need a precise business definition:

• Should the axis month remain active?
• Should only the slicer’s range be ignored?
• Are slicer and axis using different columns?
• Is the intended result a running total or a fixed benchmark?

Sometimes a disconnected date selector is appropriate because it lets
the measure explicitly apply the selection while the axis remains
independent. Do not use it as a shortcut without testing totals and
interactions.

Why the measure
still changes with the slicer

Possible causes:

• the slicer uses a different column;
• the same business attribute filters through another table;
• a nested measure reapplies the selection with
  TREATAS;
• the slicer changes a parameter used by the measure;
• the selection affects another dimension correlated with the result;
  or
• a visual calculation happens after the DAX measure.

Add:

Debug Selected Color Count =
COUNTROWS ( VALUES ( Product[Color] ) )

Then compare the count inside and outside the filter-removing
measure:

Debug Colors After Removal =
CALCULATE (
    COUNTROWS ( VALUES ( Product[Color] ) ),
    REMOVEFILTERS ( Product[Color] )
)

The second measure should show the full visible color set under the
remaining filters.

Why the measure
ignores too many filters

Search for broad modifiers:

ALL ( Product )

REMOVEFILTERS ()

ALLEXCEPT ( Product, Product[Category] )

Also inspect referenced measures. A wrapper can be narrow while its
base measure already removes filters.

Compare the functions in ALL vs ALLSELECTED vs
ALLEXCEPT. If the opposite problem is occurring, follow Power BI measure ignores a
slicer.

A filter-preservation test

Create a small grid:

Test	Color	Category	Date	Expected behavior
A	One	All	All	Ignore Color
B	One	Bikes	All	Keep Bikes
C	One	Bikes	One month	Keep Bikes and month
D	Multiple	Bikes	One month	Ignore all selected Colors
E	Clear	Bikes	One month	Match base measure

Run the five states before publishing the measure. A correct result
in one screenshot does not prove the filter contract.

Frequently asked questions

Should I
use ALL or REMOVEFILTERS to ignore one slicer?

For a clear filter-removal instruction,
REMOVEFILTERS ( Table[Column] ) is usually easiest to read.
ALL ( Table[Column] ) can also clear that column and
additionally serves as a table expression in other patterns.

Can I ignore a
slicer for only one measure?

Yes. Wrap that measure in CALCULATE and remove only the
slicer column. Other measures in the same visual can continue to respond
normally.

Why does
REMOVEFILTERS ignore my category too?

You probably removed the entire Product table rather than the Color
column, or Category depends on the same combined filter path. Narrow the
removal and test visible values.

Where can I verify the
filter contract?

Use the DAX
playground. Put the base measure, modified measure, visible-color
count, and visible-fact-row count in one test table.