Power BI Course
Slicers and Filters
Slicers and filters are how users interact with a Power BI report to explore their data. They look similar — both restrict what the visuals show — but they live in different places, behave differently, and serve different purposes. Knowing when to use a slicer versus a filter, how to sync slicers across pages, and how to control visual interaction settings gives you complete control over the user experience of your reports.
Slicers vs Filters — The Core Difference
Slicer Types
Power BI offers seven slicer styles, selectable from the slicer's Format pane under Visual → Slicer settings → Options → Style. Each style has a different optimal use case. Choosing the right style reduces friction for the user.
Slicer Interactions — What Gets Filtered
By default a slicer cross-filters every other visual on the same page. Sometimes this is not what you want — a "sparkline for context" visual should remain unfiltered while the main charts respond to the slicer. Edit Interactions lets you control exactly which visuals respond to which slicers.
Sync Slicers Across Pages
By default a slicer only filters the page it lives on. When a user navigates to another page, the slicer resets. Sync slicers solves this — the slicer selection persists across every page you configure, so selecting 2024 on the Summary page still shows 2024 data on the Detail page.
Filter Pane Scope Levels
// Three filter scope levels — applied in the Filter Pane
// Visual-level filter
// Drag a field to "Filters on this visual" in the Filter pane
// Only the selected visual is affected
// Example: a "Top Products" bar chart filtered to Revenue > 10,000
// Other visuals still show all products
// Page-level filter
// Drag a field to "Filters on this page"
// Every visual on the current page is affected
// Navigating to another page resets this filter
// Example: a page showing only 2024 data
// Report-level filter
// Drag a field to "Filters on all pages"
// Every visual on every page in the report is affected
// Persists as user navigates between pages
// Example: always exclude Status = "Test" or "Cancelled"
// Locking a filter (prevents users from changing it)
// In the Filter pane: hover the filter → lock icon (padlock) → click
// Locked filters are visible but the user cannot change the value
// Use for data quality filters like Status <> "Cancelled"
// Hiding a filter (invisible to users in reading view)
// In the Filter pane: hover the filter → eye icon → click
// Hidden filters apply silently — the user does not know they exist
// Use with caution — hidden filters can cause confusion
// when reported totals do not match expectationsSlicer Formatting Best Practices
// Slicer header — rename to guide the user
// Format pane → Visual → Slicer header → Title text
// Change "Region" to "Filter by Region ▾" or "Select Region"
// This tells the user what to do, not just what the field is
// Search box — enable for long lists
// Format pane → Visual → Slicer settings → Show search box
// Appears when the slicer has more than ~10 items
// User can type to filter the slicer list
// Select All option — enable when multi-select is expected
// Format pane → Visual → Slicer settings → Show "Select all" option
// Adds a checkbox at the top that selects/deselects everything at once
// Slicer orientation — horizontal for top-of-page filters
// Format pane → Visual → Slicer settings → Orientation → Horizontal
// Combined with tile style this creates a compact tab-style filter bar
// Clear button — always leave enabled
// Format pane → Visual → Slicer settings → Show clear button (eraser)
// The × button lets users reset without knowing they need to click
// each item individually. Remove it only for forced single-select flows.
// Default value — set a specific starting selection
// Right-click the slicer → Edit interactions will not set a default
// Instead: make the selection → File → Options → Current file →
// Query reduction → "Apply" button, or use bookmarks (Lesson 45)Teacher's Note: The most important interaction setting that developers forget is Edit Interactions on the "overall total" card visual. Almost every dashboard has a card showing the grand total revenue. When a user selects a region in a slicer, the grand total card should change to show that region's revenue — but sometimes you want a separate "Grand Total (all regions)" card for comparison. If you want it to stay fixed, select the slicer → Format → Edit interactions → click the None icon on that card. Now the region slicer cross-filters every chart except the reference total card. This single setting transforms a confusing dashboard into a clear one.
Practice
Practice 1 of 3
To make a slicer's filter selection persist when a user navigates from the Summary page to the Detail page — without showing a second slicer on the Detail page — you set the Detail page's Sync toggle to On and its Visible toggle to ___ in the Sync slicers panel.
Practice 2 of 3
To prevent a "Grand Total (all regions)" reference card from being filtered when a user selects a region in a slicer, you select the slicer → Format → Edit interactions → click the ___ icon on that card visual.
Practice 3 of 3
A filter that permanently excludes test orders (Status = "Test") from the entire report — applied by the developer and invisible to end users — is best applied as a ___ filter in the Filter pane and then hidden using the eye icon.
Lesson Quiz
Quiz 1 of 3
A report has a Year slicer and a Region slicer on the Summary page. On the Detail page a line chart shows monthly revenue but ignores the Year slicer entirely — it always shows all years. The Region slicer works correctly on the Detail page. What is the most likely cause?
Quiz 2 of 3
You want a bar chart to grey out non-matching bars when a slicer selection is made — keeping all bars visible but highlighting the selected ones — rather than filtering out the non-matching bars entirely. Which Edit Interactions setting achieves this?
Quiz 3 of 3
A report-level filter excludes Status = "Cancelled" from all pages. A user tells you the total order count they see in the report (342) does not match the number they see in their CRM system (389). What is the most likely explanation?
Next up — Lesson 44 covers Custom Tooltips, explaining how to build tooltip pages that display rich multi-measure context when a user hovers over any data point in a visual.