Study guide

7.4 Report Page Configuration and Slicers

Microsoft Power BI Data Analyst PL-300

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the PL-300 Exam The Power BI Ecosystem

2 Chapter 1: Get or Connect to Data

1.1 Data Source Types and Connections 1.2 Storage Modes: Import, DirectQuery, and Direct Lake 1.3 Data Source Settings and Parameters

3 Chapter 2: Profile and Clean the Data

2.1 Data Profiling in Power Query 2.2 Resolving Errors, Nulls, and Data Quality Issues 2.3 Data Types and Type Detection

4 Chapter 3: Transform and Load the Data

3.1 Column Transformations and Data Types 3.2 Grouping, Aggregating, Pivoting, and Unpivoting 3.3 Merge Queries, Append Queries, and Relationship Keys 3.4 Query Folding and Load Performance

5 Chapter 4: Design and Implement a Data Model

4.1 Star Schema Design 4.2 Relationships, Cardinality, and Cross-Filter Direction 4.3 Table and Column Properties 4.4 Calculated Columns and Calculated Tables

6 Chapter 5: Create Model Calculations with DAX

5.1 DAX Fundamentals and Measures 5.2 The CALCULATE Function 5.3 Time Intelligence Measures 5.4 Statistical Functions, Semi-Additive Measures, and Calculation Groups 5.5 Essential DAX Patterns and Functions Reference

7 Chapter 6: Optimize Model Performance

6.1 Performance Analyzer and DAX Query View 6.2 Model Size Reduction and Cardinality Management 6.3 DAX Optimization Patterns

8 Chapter 7: Create Reports

7.1 Visual Types and Selection 7.2 Visual Formatting and Conditional Formatting 7.3 Copilot in Power BI Reports 7.4 Report Page Configuration and Slicers

9 Chapter 8: Enhance Reports for Usability and Storytelling

8.1 Bookmarks, Navigation, and Drillthrough 8.2 Sorting, Selection Pane, Mobile Layout, and Accessibility 8.3 Export Settings and Automatic Page Refresh

10 Chapter 9: Identify Patterns and Trends

9.1 The Analyze Feature and AI Visuals 9.2 Using Copilot to Summarize the Semantic Model 9.3 Advanced Analytics Patterns

11 Chapter 10: Create and Manage Workspaces and Assets

10.1 Workspaces, Apps, and Content Distribution 10.2 Subscriptions, Alerts, and Semantic Model Refresh 10.3 Dashboards and Advanced Distribution

12 Chapter 11: Secure and Govern Power BI Items

11.1 Row-Level Security (RLS) 11.2 Sensitivity Labels, Item Access, and Governance 11.3 Deployment Pipelines and Content Lifecycle

7.4 Report Page Configuration and Slicers

Key Takeaways Explain This Topic AI

Slicers filter interactively and come in list, dropdown, between (range), date range, relative date, and hierarchy styles.

Sync slicers let one slicer control multiple pages, with independent control over which pages it syncs to and is visible on.

Visual interactions (Edit Interactions) set how selecting in one visual affects others: Filter, Highlight, or None.

The filter pane offers visual-, page-, and report-level filters; visual-level overrides page-level for that visual.

Page settings control page size (16:9, 4:3, Letter, custom), background, navigation, and bookmarks.

Last updated: June 2026

Quick Answer: Slicers are interactive filter controls. Key types: list (checkboxes), dropdown, range (between), relative date ("last 30 days"), and hierarchy. Sync slicers to share filtering across pages. Configure visual interactions (Format > Edit Interactions) to control how clicking one visual affects others.

Slicers

  • Type Appearance Best For
  • List Checkboxes Few categories
  • Dropdown Collapsed list Many categories (saves space)
  • Between Two-handle slider Numeric ranges
  • Date range Calendar picker Date selections
  • Relative date "Last N days/months/years" Rolling periods
  • Relative time "Last N hours/minutes" Real-time dashboards
  • Hierarchy Expandable tree Multi-level filtering

Configure single vs. multi-select (hold Ctrl to multi-select in single-select mode), enable a search box for long lists, and show/hide Select All . A relative date slicer (set, for example, to "Last 30 Days") recalculates against today's date automatically, so the dashboard never needs manual date updates, ideal for always-current views.

Sync Slicers

View > Sync slicers lets one slicer control filtering on multiple pages.

  • Setting Meaning
  • Sync (lightning bolt) The slicer's selection applies to this page
  • Visible (eye) The slicer appears on this page

A common pattern: a Year slicer visible on Page 1 that syncs (but is hidden) on Pages 2-5, so every page filters to the same year while the control shows only once.

Visual Interactions

Select a visual, then Format > Edit interactions , and choose how it affects each other visual.

  • Type Behavior
  • Filter The other visual shows only matching data
  • Highlight The other visual highlights matches, dims the rest
  • None The other visual is unaffected

Defaults: charts Highlight ; tables, matrices, and maps Filter ; slicers always Filter . Set None when a KPI card should always show the total regardless of selections; set Filter for strict drill-down between related visuals; keep Highlight for exploratory dashboards where context matters.

Filter Pane

  • Level Scope
  • Visual-level Only the selected visual
  • Page-level All visuals on the current page
  • Report-level All visuals on all pages

You can lock filters (users cannot change them), hide them while keeping them active, require single selection, and search within values. A visual-level filter overrides the page-level filter for that one visual.

Page Configuration

  • Page Size Dimensions Use Case
  • 16:9 1280 x 720 Standard widescreen (default)
  • 4:3 960 x 720 Presentation/projection
  • Letter 816 x 1056 Print-ready portrait
  • Custom User-defined Specific device/display

Page settings also control background color/image and transparency, and navigation via the page navigator button bar, custom buttons with actions, and bookmarks that save page state (filters, selections, visibility) for guided storytelling. Under report settings you can allow or deny export to PDF, PowerPoint, and image, and control copying or exporting underlying data.

On the Exam

The PL-300 tests choosing the correct slicer type, configuring sync slicers across pages, setting visual interactions (Filter/Highlight/None), the filter-pane levels (visual/page/report), and the difference between filter and highlight.

Pages Are Designed Experiences, Not Just Canvases

Report-page configuration is where a model becomes a usable product. The decisions, which slicers, how visuals interact, what the filter pane exposes, how pages are sized and navigated, determine whether a business user can answer their questions without confusion. The PL-300 "create reports" objective tests these choices directly, so you should be fluent in the trade-offs: a dropdown slicer to save space versus a list slicer for visibility, a relative-date slicer for an always-current view versus a fixed range for a point-in-time report, and sync slicers to keep multipage reports coherent.

Visual Interactions Are the Heart of Interactivity

The default cross-filtering behavior, click a bar and watch related visuals respond, is powerful but must be shaped deliberately. Charts default to Highlight , while tables, matrices, and maps default to Filter , and slicers always filter. Setting an interaction to None is the standard fix when a KPI card or total should stay constant regardless of selections; setting Filter enforces strict drill-down between related visuals; keeping Highlight preserves context for exploratory dashboards.

Recognizing which interaction a described behavior requires, "the total should not change when I click a bar" implies None, is a high-frequency exam pattern.

Filter Scopes and Sync Compose Cleanly

The filter pane's three scopes layer predictably: report-level filters apply everywhere, page-level filters refine a single page, and visual-level filters refine one visual on top of the broader scopes. Filters combine (narrower refines broader) rather than fighting, so a visual-level filter takes effect within whatever report-level filter is active. Sync slicers add a second axis of control by separating which pages a slicer affects (Sync) from which pages it appears on (Visible), enabling the common "one Year slicer visible on the landing page but driving every page" design.

Understanding how scopes and sync compose lets you predict the data each visual will show, which is exactly what the configuration questions ask.

Bookmarks, Buttons, and Guided Navigation

Beyond slicers and interactions, polished reports use bookmarks and buttons to script an experience. A bookmark captures the current page state, applied filters, slicer selections, the visible/hidden set of visuals, and the current spotlight, so you can build toggles (switch a visual between chart and table), reset-filter buttons, and step-through narratives. Pairing bookmarks with the selection pane (to show and hide specific visuals) and buttons (with navigate or bookmark actions) lets one canvas serve several views without crowding.

The page navigator auto-generates a button bar across pages, and custom buttons can deep-link to a specific page or apply a bookmark. These tools, together with page size presets and backgrounds, are how you turn a set of visuals into a coherent, navigable application, and the exam expects familiarity with what each mechanism does and when to choose it.