14 Filters & Slicers

The Two Tools for Controlling What Data Is Visible

Power BI provides two distinct mechanisms for restricting the data that appears in a report: filters and slicers. Both narrow down which rows of data are used in calculations and visuals, but they operate differently, live in different places, and serve different audiences.

Understanding both tools deeply, knowing when to use each one, and knowing how to configure them precisely is what allows you to build reports that are simultaneously focused for the average consumer and flexible for the analytical user.

flowchart LR
    A[Data Model <br> Full Dataset] --> B{Filtering <br> Mechanism}
    B --> C[Filters Pane <br> Set by report builder <br> Optionally visible to consumer]
    B --> D[Slicers <br> Visible on canvas <br> Controlled by consumer]
    C --> E[Visual, Page <br> or Report scope]
    D --> F[Current page <br> or synced across pages]
    E & F --> G[Filtered View <br> Shown in Visuals]
    classDef default fill:#004466,color:#ffffff,stroke:#ffcc00,stroke-width:3px,rx:10px,ry:10px;

14.1 Understanding and Using Filters

14.1.1 Types of Filters

The Four Filter Levels in Power BI

Power BI’s filter system is hierarchical, with four distinct levels. Each level has a different scope and a different purpose. Filters at a narrower level override the broader context only for the items within their scope, while broader filters apply globally across everything beneath them.

[Insert screenshot of the Filters pane open on the right side of the canvas showing all four sections stacked: Filters on this visual, Filters on this page, Filters on all pages, and Drillthrough, each with an expand arrow and one or more filter cards inside]

Visual-Level Filters

Filters on This Visual

Visual-level filters apply to a single selected visual only. They restrict the data used in that visual without affecting anything else on the page. They are set by clicking the visual first and then adding a filter to the “Filters on this visual” section of the Filters pane.

When to use them: When one specific chart needs to show a restricted subset of data that differs from the rest of the page. For example, a “Top 10 Products” bar chart on a page that otherwise shows all products, or a line chart restricted to the current year on a page where other visuals show all years.

[Insert screenshot of the Filters pane with a visual selected, showing the “Filters on this visual” section expanded with a filter card on the Revenue field set to “is greater than 50000”]

Page-Level Filters

Filters on This Page

Page-level filters apply to all visuals on the current page. They act like an invisible, always-on slicer for the entire page. When a page-level filter is active, every visual on that page reflects it without any slicer being visible on the canvas.

When to use them: When an entire page is dedicated to a specific context that should always be enforced, such as a page that always shows only the current financial year, or a regional analysis page that always filters to one country, without exposing the filter control to the consumer.

[Insert screenshot of the Filters pane with no visual selected, showing the “Filters on this page” section expanded with a Year filter set to 2025]

Report-Level Filters

Filters on All Pages

Report-level filters apply to every visual on every page throughout the entire report. They are permanent constraints that should always be in effect regardless of which page the consumer is viewing.

When to use them: Excluding test or inactive records, restricting the report to a specific business unit or data partition, or removing future-dated records that should never appear in any visual. Report-level filters are set once and apply everywhere without the consumer being aware of them.

[Insert screenshot of the Filters pane showing the “Filters on all pages” section with a Status filter set to “is not Test” and a “is not Inactive” condition]

Drillthrough Filters

Drillthrough filters appear on drill-through detail pages and represent the value that the consumer right-clicked on to arrive at the page. Power BI automatically applies the drillthrough filter when the consumer navigates to the detail page, restricting all visuals on that page to the selected context.

Drillthrough filters are not manually configured in the Filters pane in the same way as other filters. They are defined by the fields placed in the Drillthrough field well of the detail page (covered in Chapter 8) and are applied automatically at navigation time.

[Insert screenshot of a drill-through page showing the Drillthrough section in the Filters pane with the drillthrough field value automatically populated (e.g., “ProductCategory is Electronics”), alongside the Back button in the top-left corner]

14.1.2 The Filter Pane in Depth

Basic Filtering

The simplest filter configuration in the Filters pane is a basic filter, which presents a list of unique values from the selected field as checkboxes. The consumer (or builder) checks the values to include and unchecks values to exclude.

To apply a basic filter:

In the Filters pane, expand a filter card by clicking its name
A list of unique values appears with checkboxes
Check the values to include. All unchecked values are excluded from the visual, page, or report (depending on the filter level)
The filter card header shows the active filter condition in grey text beneath the field name

[Insert screenshot of a basic filter card in the Filters pane showing a list of Region checkboxes with three of five regions checked (North, South, East) and two unchecked (West, Central)]

Advanced Filtering

Advanced filtering switches the checkbox list to a rule-based condition interface where you can express more precise filter logic using text, numeric, or date operators.

To switch to advanced filtering:

Expand a filter card in the Filters pane
Click the Advanced filtering toggle (shown as a dropdown or switch at the top of the filter card)
Set the condition type from the dropdown: “contains”, “does not contain”, “starts with”, “is”, “is not”, “is blank”, “is not blank”, and others depending on the field data type
Enter the filter value in the text or numeric field below the condition
Optionally add a second condition with AND or OR logic by clicking Add filter
Click Apply filter

[Insert screenshot of an advanced filter card showing a text field with the condition “ProductName contains ‘Pro’” with an “Apply filter” button below]

Top N Filtering

Top N filtering restricts a visual to show only the top or bottom N values of a measure, ranked automatically. This is distinct from manually selecting values in a basic filter and is recalculated dynamically as other filters and slicers change.

To apply a Top N filter:

Expand a filter card in the Filters pane for the field you want to rank by
Switch the filter type to Top N
Set Show items to “Top” or “Bottom”
Enter the number of items to show (such as 5 or 10)
In the By value section, drag or select the measure to rank by (such as Total Sales or Revenue)
Click Apply filter

[Insert screenshot of a Top N filter card showing “Top 5” selected, “By value: Total Sales” configured, and an Apply filter button, alongside the bar chart on the canvas showing only the five highest-revenue products]

Lock or Hide Individual Filters to Control Consumer Experience

For each filter card in the Filters pane, click the lock icon to lock it (consumers can see it but cannot change it) or the eye icon to hide it (consumers cannot see or change it). Locking is useful for filters you want consumers to know are active but not modify. Hiding is useful for technical filters (such as excluding test data) that would confuse consumers if visible.

[Insert screenshot of a filter card header showing the lock icon and eye icon in the top-right corner, with one card locked and one hidden, illustrated with the corresponding icons in their active states]

14.2 Slicer Types

14.2.1 Slicer Types in Depth

What Determines Slicer Type

Power BI automatically selects a default slicer style based on the data type of the field placed in the slicer. A text field produces a list slicer by default. A date field produces a between (date range) slicer. A numeric field produces a numeric range slider. You can override the default by going to the Format visual panel and changing the slicer style setting. The available styles depend on the field type.

List Slicer

The list slicer displays all unique values in the field as a scrollable list with checkboxes. It is the default slicer style for text fields and the most commonly used slicer type in Power BI reports.

By default, selecting one item filters the report to that item only. Holding Ctrl while clicking allows multiple selections. Alternatively, enable Multi-select with CTRL or Select all options in the slicer settings to give consumers more control.

[Insert screenshot of a list slicer showing five region names with checkboxes, three of which are checked, and a “Select all” checkbox at the top]

Between Slicer (Date Range and Numeric Range)

Between Slicer

The between slicer renders as two input fields (From and To) or as a draggable range slider. For date fields, it shows a date picker that lets consumers select a start and end date. For numeric fields, it shows a slider or numeric input for selecting a value range.

Between slicers are the standard control for date range filtering and numeric threshold filtering, allowing consumers to precisely define the boundaries of their analysis without scrolling through a long list.

[Insert screenshot of a between slicer showing a date range picker with a start date of 01/01/2025 and an end date of 31/12/2025 selected, with calendar navigation arrows visible]

Relative Date Slicer

The relative date slicer filters data to a rolling time window relative to today’s date, without requiring the consumer to manually update the date range each day. Options include “last N days/weeks/months/years”, “this week/month/quarter/year”, “next N days/weeks”, and so on.

This is the ideal slicer type for operational dashboards that should always show the most recent period: last 30 days of orders, this month’s activity, or the last 7 days of website traffic. The filter window moves forward automatically as the date changes, with no manual intervention required.

To set up a relative date slicer:

Place a date field in the slicer’s Field well
In the Format visual panel, expand Slicer settings and change the Style to Relative date
Configure the rolling window: the anchor (Last, This, Next), the number, and the period (Days, Weeks, Months, Quarters, Years)

[Insert screenshot of a relative date slicer configured to “Last 30 Days” with the anchor dropdown, number input, and period dropdown visible in the slicer settings]

Tile Slicer

The tile slicer displays each unique value as a clickable rectangular button tile rather than a list item or checkbox. Clicking a tile selects it and applies the filter. Clicked tiles are visually highlighted to show the active selection.

Tile slicers are best for slicers with a small number of values (two to eight) where you want the selections to be immediately visible and easy to click, such as a Year slicer with four years or a Status slicer with three options.

[Insert screenshot of a tile slicer showing four year values (2022, 2023, 2024, 2025) as rectangular tiles, with the 2025 tile highlighted/selected in a contrasting colour]

Hierarchy Slicer

When multiple fields from the same dimension are placed in a single slicer’s Field well, Power BI creates a hierarchy slicer. The slicer shows the top level of the hierarchy (such as Country) as expandable nodes. Clicking the expand arrow reveals the next level (State or Region), and expanding further reveals the lowest level (City).

Hierarchy slicers allow consumers to filter at multiple levels of granularity from a single slicer control, without needing three separate slicers for Country, State, and City.

To create a hierarchy slicer:

Place a slicer on the canvas
Drag the highest-level field into the Field well (such as Country)
Drag additional levels into the same Field well beneath it (State, then City)
The slicer automatically displays the hierarchy with expand/collapse controls

[Insert screenshot of a hierarchy slicer showing India as a top-level node with an expand arrow, expanded to show Telangana and Karnataka as child nodes, with Telangana further expanded to show Hyderabad and Warangal as city-level values]

14.3 Slicer Configuration and Behaviour

14.3.1 Slicer Formatting and Styling

Formatting Slicers for a Polished Look

Slicers are prominent interactive elements that consumers interact with directly, so their visual appearance matters for both usability and report aesthetics. The Format visual panel for a selected slicer provides controls for every aspect of its appearance.

Key formatting options include:

Slicer header — toggle the header on or off, and customize its text, font, size, colour, and background
Values — control the font family, size, colour, and background of the individual items in the list or tiles
Selection controls — show or hide a “Select all” checkbox and configure multi-select behavior
Background — set the background colour and transparency of the slicer visual itself
Border — add a border around the slicer with a custom colour, width, and corner radius

[Insert screenshot of a styled slicer with a dark navy header reading “Select Region”, white item text on a dark background, and a subtle border with rounded corners, alongside the Format visual panel showing the relevant settings]

Match Slicer Colours to Your Report Theme

Slicers that are styled consistently with the rest of the report (matching header colours, fonts, and border styles) feel like an integrated part of the design rather than an afterthought. Set slicer backgrounds and header colours to match the section background colours used in your report layout. Apply the same font family used in your chart titles. This small effort makes the report feel cohesive and professionally designed.

14.3.2 Syncing Slicers Across Pages

What Is Slicer Sync?

By default, a slicer on Page 1 only affects visuals on Page 1. When the consumer navigates to Page 2, the slicer state is not carried forward and the Page 2 visuals show unfiltered data. Slicer sync allows a slicer to maintain its selection across multiple pages, giving consumers a consistent filter experience as they move through the report.

Sync is configured separately for each slicer. You can choose which pages a slicer syncs to and whether the slicer is visible on each of those pages.

How to Sync a Slicer

Select the slicer you want to sync on the canvas
Go to the View ribbon and click Sync slicers to open the Sync slicers panel
The panel lists all pages in the report as rows, with two columns of toggles: Sync (the slicer value applies to this page) and Visible (the slicer control is visible on this page)
Toggle Sync on for every page that should reflect this slicer’s selection
Toggle Visible on for pages where you want the slicer control to appear, and leave it off for pages where the filter should apply silently without a visible slicer

[Insert screenshot of the Sync slicers panel showing a list of five report pages as rows, with Sync toggles enabled on four pages and Visible toggles enabled on three of those four pages, indicating that one page receives the filter without displaying the slicer control]

Create One Slicer Panel Page and Sync It Everywhere

A clean technique for large reports is to design a single consistent slicer panel (a narrow column of slicers on one side of the canvas) on your first report page, then sync all slicers to every subsequent page and set them as visible on all pages. This ensures consumers always see the same slicer controls in the same position on every page, making the filter experience predictable and consistent throughout the entire report.

14.3.3 Cascading Slicers

What Are Cascading Slicers?

Cascading slicers (also called dependent slicers) are a configuration where selecting a value in one slicer automatically filters the available options in a second slicer. For example, selecting “India” in a Country slicer causes the State slicer to show only Indian states, and selecting “Telangana” in the State slicer causes the City slicer to show only Telangana cities. Each slicer’s options cascade based on the selection made in the parent slicer above it.

This behavior is not a special feature that needs to be enabled. It happens naturally in Power BI when the slicer fields belong to a dimension table with a proper hierarchy and the relationships in the model are correctly configured with single cross-filter direction from the dimension to the fact table.

How Cascading Works in the Data Model

Cascading occurs because slicers filter each other through the data model relationships. When you select “India” in the Country slicer, that selection filters the DimLocation table to Indian rows. The State slicer, which also draws its values from DimLocation, now only sees the states that exist in the filtered (Indian) rows. The cascade is automatic and requires no special configuration beyond a clean, normalized dimension table with country, state, and city as separate columns.

[Insert screenshot showing three slicers side by side: a Country slicer with “India” selected, a State slicer now showing only Indian states, and a City slicer showing only cities in the selected state, demonstrating the cascading filter effect]

Bidirectional Relationships Can Break Cascading

If the relationship between your dimension table and fact table is set to Both (bidirectional) cross-filter direction, the fact table also filters the dimension table, which can cause the State slicer to show only states that appear in the fact table (those with transactions) rather than all states in the dimension table. This produces inconsistent cascading behavior. To avoid this, keep all relationships between dimension and fact tables set to Single direction.

14.3.4 Search Within Slicers

Enabling Search in a Slicer

For slicers with many values (product catalogues with hundreds of products, customer lists with thousands of names, city slicers spanning an entire country), scrolling through the full list to find a specific value is impractical. Power BI provides a search bar within list and dropdown slicers that allows consumers to type and instantly filter the slicer list to matching values.

To enable the search bar:

Select the slicer on the canvas
Click the three-dot More options menu in the top-right corner of the slicer header
Select Search from the menu. A search input bar appears at the top of the slicer list

Once enabled, consumers can type any text into the search bar and the slicer list narrows to show only values containing that text. The search is case-insensitive and matches anywhere within the value (not just at the start).

[Insert screenshot of a list slicer with the search bar enabled, showing a text input at the top with “bang” typed in, and the slicer list filtered to show only “Bangalore” from a longer list of city names]

Enable Search by Default for Any Slicer with More Than 10 Values

As a general rule, enable the search bar on any slicer that has more than ten unique values. Consumers finding a value in a ten-item list is straightforward. Finding a value in a hundred-item list without search is frustrating. The search bar adds no visual noise when not in use and dramatically improves usability for longer lists.

14.3.5 Clear Filters and Reset Buttons

Clearing Individual Slicers

Each slicer has a built-in clear control that removes the current selection and returns the slicer to its default “all values selected” state. It appears as a small eraser icon in the top-right corner of the slicer header, visible when the slicer is hovered over or selected.

Consumers can click this icon to clear their selection from a single slicer without affecting selections in other slicers on the page.

[Insert screenshot of a slicer with the mouse hovering over it, showing the eraser clear icon appearing in the top-right corner of the slicer header]

Building a “Reset All Filters” Button

For reports where consumers apply multiple slicers and filters during exploration, providing a single “Reset All Filters” button that clears every slicer on the page simultaneously is a major usability improvement. This is built using Bookmarks.

To create a Reset All Filters button:

Set all slicers on the page to their default state (no selections active, all values showing)
Open the Bookmarks panel (View → Bookmarks) and click Add to create a bookmark of this clean state. Name it “Reset State”
Go to the Insert ribbon and click Buttons → Blank to add a button to the canvas
Label the button “Reset Filters” using the Format button panel
In the Format button panel, expand Action, toggle it On, set Type to Bookmark, and select the “Reset State” bookmark
When consumers click the button, all slicers return to their unselected default state instantly

[Insert screenshot of a report page showing a “Reset Filters” button in the top-right corner of the slicer panel, with the Format button panel open on the right showing the Bookmark action configured to the Reset State bookmark]

Always Include a Reset Button on Consumer-Facing Reports

Reports shared with non-technical consumers often get into confusing states where multiple slicers have been clicked and the consumer cannot easily restore the default view. A clearly labelled Reset Filters button eliminates this frustration entirely. Place it in a consistent, prominent position (such as next to the slicer panel or in the report header) on every page of the report.

14.4 Filters, Slicers, and DAX

14.4.1 How Filters Affect DAX Measures

Filters and Slicers Create the Filter Context

Every filter and slicer selection in a report modifies the filter context in which DAX measures are evaluated. When a consumer selects “North” in a Region slicer, every measure on the page is recalculated with North as an active filter. [Total Sales] returns only North region sales. [Average Order Value] returns the average for North only. This dynamic recalculation is the core of Power BI’s interactivity and it is powered entirely by DAX’s filter context model.

Understanding this connection is important because it determines how measures behave when filters are applied, and it explains why certain measures need to use CALCULATE to override or extend the filter context in specific ways.

[Insert screenshot showing a report page in two states side by side: on the left with no slicer selection showing grand total values in all visuals, and on the right with “North” selected in the Region slicer showing recalculated values across all visuals]

Measures That Ignore Slicers

Some measures are designed to always return the same value regardless of slicer selections. These use CALCULATE with ALL or ALLSELECTED to remove or expand the filter context:

Code

-- Always returns the grand total regardless of slicer selections
Grand Total Sales =
    CALCULATE([Total Sales], ALL(FactSales))

Code

-- Returns the total for all currently visible values in the slicer
-- (respects the slicer's visible set but ignores individual item selection)
Total for Visible Regions =
    CALCULATE([Total Sales], ALLSELECTED(DimRegion[RegionName]))

Practical example: A report shows regional sales alongside a grand total benchmark. The Grand Total Sales measure always shows the company-wide total, even when the consumer selects a specific region in the slicer. This lets the consumer compare their selected region’s performance against the fixed company-wide figure.

Slicers vs. Visual-Level Filters in DAX

Both slicers and visual-level filters reduce the filter context for the visuals they apply to, and DAX measures respond identically to both. From a DAX perspective, there is no difference between a consumer selecting “2025” in a Year slicer and a report builder applying a “Year is 2025” visual-level filter. Both result in the same filter context being passed to the measure at query time.

The difference is entirely about who controls the filter and when: slicers give control to the consumer at runtime, while visual-level filters are set by the builder at design time and (unless unlocked) cannot be changed by the consumer.

14.5 Making the Right Choice

14.5.1 Slicers vs. Filter Pane: When to Use Which

Choosing the Right Tool for Each Filtering Need

The choice between a slicer and a filter pane filter is a design decision that depends on your audience, the purpose of the filter, and how much control you want to give the consumer.

Scenario	Use a Slicer	Use the Filter Pane
Consumer needs to interactively change the filter	Yes	No
Filter should always be on and never changed	No	Yes (hidden)
Filter should be visible but locked	No	Yes (locked)
Multiple pages need the same filter control	Yes (sync)	Yes (report-level)
Filter involves a date range the consumer picks	Yes (between/relative)	No
Filter excludes test or system data	No	Yes (hidden, report-level)
Filter is used by non-technical consumers	Yes	Rarely
Canvas space is very limited	No (use filter pane)	Yes

Filters and Slicers Work Best Together

The most effective Power BI reports combine both tools deliberately. Use the filter pane for background constraints that keep the data clean and focused (hidden report-level filters for test data exclusion, locked page-level filters for page-specific context). Use slicers for the interactive controls the consumer is meant to use for exploration. This separation gives the report builder full control over data integrity while giving the consumer full freedom within the intended analytical space.

Summary

Concept	Description
Filter Mechanics
Filter Pane Levels	Visual-, page-, and report-level filter scopes
Slicers	Visual filter controls placed directly on the canvas
Sync Slicers	Slicers that update other pages or visuals at once
Drill-Through Filters	Filters automatically applied when navigating via drill-through
Top N Filters	Restricting visuals to top or bottom N members of a category
Patterns and Practice
Relative Date Filters	Last 7 days, this month, year-to-date, and similar quick filters
Hierarchy Slicers	Slicers that allow selection across hierarchy levels
Filter Best Practices	Avoid too many slicers per page; prefer search-friendly slicers