Slicers and Filters

Analogy categoryAnalogies

Power BI offers three layers of filtering-slicers, visual-level filters, and page/report-level filters-that combine using AND logic to narrow the data any visual displays; slicers are visible, interactive controls on the canvas, while filters live in the Filters pane and are often hidden from end users.

🏏

Cricket analogy: Stacking a Team slicer with a Season filter and a page-level Format filter narrows the data the way a bowler's dismissal is narrowed by pitch conditions, batsman weakness, and match situation all applying together, not separately.

Slicer Types and When to Use Them

List and dropdown slicers work for low-cardinality categorical fields like Region or Product Category, while a between-range slicer or date slicer suits continuous numeric or date fields such as Order Date; hierarchy slicers let users drill from Year to Quarter to Month within a single control.

🏏

Cricket analogy: A dropdown slicer listing IPL teams (CSK, MI, RCB) suits low-cardinality selection, while a date-range slicer for "matches between March and May" handles continuous match dates, and a hierarchy slicer drills Season > Team > Player in one control.

Sync Slicers (View > Sync Slicers) lets one slicer control multiple report pages without being visible on each one, which is essential for consistent cross-page filtering in multi-page reports; without syncing, users must re-select filters on every page, which increases drop-off in self-service scenarios.

🏏

Cricket analogy: Syncing a "Season" slicer across a Batting, Bowling, and Fielding page means a selection made once carries through, the way a match referral decision (DRS) applies consistently across every camera feed reviewing the same ball.

Filter Pane vs. Visual Interactions

Visual-level filters apply only to a single visual and are useful for exceptions-like showing a Top 10 Customers table while the rest of the page stays unfiltered-whereas page-level and report-level filters cascade down to every visual, so changing a report filter can silently alter numbers everywhere.

🏏

Cricket analogy: A visual-level filter showing only the "Top 10 Run Scorers" table leaves every other visual on the page unfiltered, the way a highlights reel focuses on a few batsmen without changing the full scorecard shown elsewhere.

Advanced Filtering: Drillthrough Filters and DAX-Based Filters

Filters can also be driven by measures using visual-level "Top N" or relative date filtering, and DAX functions like KEEPFILTERS or REMOVEFILTERS inside a measure change how a visual's existing filter context is respected or overridden, which is essential when building measures that must ignore a slicer selection (e.g., "% of Total").

🏏

Cricket analogy: A "% of Team Total" measure using REMOVEFILTERS ignores the current batsman slicer to always divide by the full team score, the way a strike rate is always calculated against that batsman's own balls faced, not the whole innings.

High-cardinality fields (like a Customer ID with 500,000 distinct values) make poor slicer choices-they slow report load and overwhelm users; prefer a searchable dropdown slicer or a text-search visual, and consider a hierarchy slicer to reduce the visible option count.

If "Edit interactions" (Format tab > Edit interactions) is accidentally set to "None" between two visuals, clicking a data point in one visual will not filter the other, which looks like a bug to end users but is actually an interaction setting silently disabled during report design.

DAX

% of Portfolio =
VAR SelectedValue = SUM(Holdings[MarketValue])
VAR TotalPortfolio =
    CALCULATE(
        SUM(Holdings[MarketValue]),
        REMOVEFILTERS(Holdings[AssetClass])
    )
RETURN
    DIVIDE(SelectedValue, TotalPortfolio)

Slicers, visual filters, and page/report filters combine using AND logic.
Match slicer type to data cardinality: dropdown for short lists, range/date for continuous fields, hierarchy for drill-capable dimensions.
Sync Slicers applies one control's selection across multiple pages without duplicating the visual.
Visual-level filters create exceptions (like Top N) without affecting the rest of the page.
REMOVEFILTERS and KEEPFILTERS in DAX control whether a measure respects or overrides the active filter context.
High-cardinality fields make poor slicer candidates and should use search or hierarchy slicers instead.
"Edit interactions" set to None silently disables cross-visual filtering and is a common source of confusion.