Power BI Reports and Visuals
Where the model becomes a scannable story
Power BI reports are pages of visuals bound to the model — the rendering layer. Chart selection, formatting, drill-down, bookmarks and tooltips turn data into a scannable, actionable artifact.
What you will learn
- Choose the right visual for the message
- Use pages, drill-down, bookmarks and tooltips deliberately
- Keep reports scannable and fast
What is this?
A Power BI report is a set of pages, each a canvas of visuals bound to the model. The golden rules: one page per story, one chart type per message, interactivity via drill-down and cross-filtering, and formatting that simplifies. Reports should read top-down, answer the question, and not fight the data.
Why do you need it?
- A report's job is a decision at a glance — not a fireworks display.
- Consistent visuals and simple layout make analysis faster for everyone.
- Drill-down/bookmarks turn one model into many questions answered.
- A well-built report is cheap to maintain and survives ownership hand-offs.
Mental model
A newspaper's front page
A report page
Headline (KPI), then the story chart, a supporting table, and a clear call to action. No one buries the point under twelve fonts and twenty panels — same for your pages.
How it works
- Each visual is a query to the model with its own filter context.
- Pages organize one story each; bookmarks save exact visual states and layouts.
- Drill-down traverses hierarchies in the model; tooltips add context on hover.
- Sync-slicers and cross-filtering propagate one user interaction across the page.
- Formatter, theme and layout-clown conventions keep pages readable.
Report anatomy.
In production
- A weekly ops page: SLA KPI cards on top, a trend line, churn-by-region bars, and a store table — cross-filtered.
- An exec page uses bookmarks to toggle between 'daily', 'weekly' and 'monthly' views of one model.
- A product page uses drill-through from a funnel visual to cohort-level details via tooltips.
Best practices
- One visual, one message; interrogate 'what's the point?' for each.
- Use titles that say conclusions ('Q3 growth reversed'), not just table names.
- Sort, color and tooltip deliberately; avoid busy gridlines.
- Test on a real dataset with edge cases before publishing.
Common mistakes
- Ten visuals covering one fact family — noise instead of answer.
- Colors that encode nothing or imply good/bad without a legend.
- Publishing unreviewed bookmarks and broken drill-through paths.
- Float22 floating charts without alignment, hurting scanability.
Common issues
KPI shows blank on the service but works in DesktopRow-level security or dataset caching in the service
Verify RLS roles and refresh; test in the published workspace with a service role.
Scroll bar appears but users want filtersReport has too many visuals per page
Split into pages or use filters/tooltips instead of 20 reports on one canvas.
Debugging tips
- Blank visual? Check the dataset's refresh and the visual's filter context (page report filters).
- Order looks random? Set an explicit sort column in the visual.
- Cross-filter not working? Check 'Edit interactions' and the filter's direction.
Interview checkpoint
Hands-on lab
- Lay out a KPI + trend + breakdown page in Power BI Desktop
- Add drill-down and cross-filtering
- Verify the numbers via SQL against the same data
Wire Interactivity into a Report
45 min · intermediate
Quick quiz
The primary job of a report page visual is to:
Bookmarks let you save and reuse specific report states and layouts.