Guides

How to Use Slicers in Power BI (Filters for Readers)

By Ravindra Bagale, Power BI & Data Analytics trainer · LinkedIn · Published: 30 September 2026 · Last updated: 30 September 2026

A slicer is an on-canvas filter visual in Power BI. Readers click values (City, Year, Category) and other visuals update. Format it as list, dropdown, between or tiles, then use Edit interactions and Sync slicers when a report has multiple pages.

Slicer field → reader selection → filter context → visuals refresh

What do I need before this guide?

• A report with a fact table and a couple of visuals.
• Optional filter-context reading: CALCULATE guide.
• Course: Slicer styles.

Before and after (look at the tables first)

A slicer is a friendly filter. Click Mumbai and cards/charts that share the model drop to 150.

Why slicers beat “only Filters pane” for readers

What a slicer is: a visible filter control sitting on the report page.

Why you care:

1. Visible — people see they can click.
2. Teachable — you can say “use the City slicer”.
3. Mobile-friendlier when styled as tiles.
4. Still backed by the same filter context engine measures already obey.

Authors still use the Filters pane for locked/hidden rules. Readers live on slicers.

Tiny demo numbers:

1. Card [Total Sales] starts at 140 (Mumbai 100 + Pune 40).
2. Click Mumbai on the slicer → Card becomes 100.
3. Clear selection → 140 again.

Step-by-step: add your first slicer

What this step is: putting a City filter on the canvas and proving the Card listens.

Why you care: this is the fastest way to feel filter context.

Vertical steps:

1. Click empty canvas space.
2. Click the Slicer icon.
3. Tick or drag City (or Date[Year]).
4. Select Mumbai — watch the Card and chart.
5. Clear selection (eraser / clear control depending on version) — totals return.
6. Save the .pbix.

What Power BI does to the rows

1. Before click: both Mumbai and Pune rows are visible → SUM = 140.
2. After Mumbai: only Mumbai rows remain → SUM = 100.
3. Other visuals that share the model get the same filter (unless Edit interactions says otherwise).

What you see on screen

1. A slicer list with Mumbai and Pune.
2. Card jumping 140 → 100.
3. Column chart showing only Mumbai’s bar (or highlighting, depending on interactions).

Orientation tips

1. Too tall list? Switch to Dropdown.
2. Date range needed? Use a date field with Between style.
3. Few values and touch screen? Try Tiles.

Styles explained (classroom)

List

1. Shows many values at once.
2. Good for 5–15 cities.
3. Multi-select habits: follow your Desktop version’s Ctrl-click / selection controls — test as a reader.

Dropdown

1. Saves canvas space.
2. Great when you already have dense charts.
3. Slightly easier to miss — label it clearly (“City”).

Between

1. Perfect for dates and numeric ranges.
2. Readers drag start/end.
3. Pair with a proper Date data type (fix types in Power Query first).

Tiles

1. Big buttons.
2. Nice for Channel = Online / Store / Partner.
3. Do not use for 200 product SKUs.

Edit interactions — when one visual should not listen

What Edit interactions is

A design setting that controls whether a slicer filters, highlights, or does nothing to each other visual.

Why you need it

Sometimes a “Company total” card must stay global (always 140) while charts filter to Mumbai (100).

Vertical steps

1. Select the slicer.
2. Format / ribbon → Edit interactions.
3. On each visual, choose Filter / Highlight / None (icons).
4. Set the global KPI to None if that is the design.
5. Exit Edit interactions; test again.

What you see on screen: small icons on every visual while Edit interactions is on.

Forgetting this step is how “bug” reports are born.

Sync slicers across pages

What Sync slicers is

A setting that keeps the same slicer selection when the reader moves between report pages.

Why you need it

Multi-page reports feel broken if Page 1 says Mumbai and Page 2 silently shows all cities.

Vertical steps

1. Create the same City (or Year) slicer idea on Page 1 and Page 2 (or copy the visual).
2. View → Sync slicers pane.
3. Tick the pages that should share the selection.
4. Optionally hide the slicer on page 2 but keep it synced — advanced layout trick; label carefully so readers are not confused.
5. Change City to Mumbai on page 1; flip to page 2; confirm the filter stuck (Card still 100).

What you see on screen: Sync slicers pane with checkboxes per page.

Slicer vs Filters pane (interview clarity)

Both create filter context. They are teammates, not enemies.

FreshBasket practice scenario (fictional)

1. Page “Overview”: City slicer + KPI cards + trend (start 140).
2. Page “Cities”: same City selection synced + ranking table.
3. Page “About”: no slicer needed; company text only — do not sync nonsense here.
4. Manager opens Overview, picks Mumbai (100), jumps to Cities — still Mumbai.

Troubleshooting table

Accessibility and clarity

1. Slicer titles must be readable (City, not dim_city_name_raw).
2. Do not rely on colour alone for selection state.
3. Leave a clear “reset filters” instruction on training reports.
4. On Mobile, prefer fewer slicers and tile style.

Multi-select teaching line for class

“Hold Ctrl to select more than one city — then release and click a chart to keep exploring.” (Exact modifier keys can vary by build; always demonstrate live on your Desktop version.)

Connect to DAX learning

Every slicer click is filter context practice. When CALCULATE confuses someone, bring them back to a slicer demo for five minutes (Mumbai 100 vs all 140) — the fog usually lifts.