Drillthrough is the bridge from summary insight to focused detail.
Complete 12 of 24 practices (50%) and enter your name to unlock the Certificate of Participation.
Drill down stays inside a visual and explores hierarchy levels. Drillthrough leaves the current page and opens a dedicated target page filtered to the selected context.
An executive sees 17 overdue cases. Drill down might show division → department. Drillthrough can take one selected department to a page with case-level rows, owner, age, amount and status.
Use Drill Down when:
Year → Quarter → Month
Division → Department → Team
Use Drillthrough when:
Department KPI → Department Detail Page
Customer Bar → Customer 360 Page
Inspection Count → Inspection Record PageChoose drillthrough when users need a new page built specifically for the selected entity or record.
A drillthrough page is a normal report page with drillthrough fields added to its filter well. Those fields define the context Power BI must receive before the page becomes a valid target.
If the source page answers 'Which departments are late?', the target should answer 'Which cases make this department late, who owns them, and what should I inspect next?'
Page: Customer Detail
Drillthrough fields:
- CustomerID
Visuals:
- Customer Name / Segment
- Total Sales
- Open Issues
- Recent Transactions
- Detail Table
- Trend by MonthA strong target page does not repeat the source page; it advances the analysis.
Drillthrough only works when Power BI can match the source selection to the target page's drillthrough fields. If the required field is not part of the source visual's context, the drillthrough destination may not appear.
A chart showing Sales by Region can drill to Region Detail because Region is in the visual context. It cannot reliably drill to CustomerID unless the source context provides CustomerID.
Target requires: DepartmentID
Source visual should include context for:
DepartmentID
(or a field/model path that correctly provides it)
Test:
Right-click selected point
→ Drillthrough
→ Target page appears
→ Target visuals show only expected departmentIf drillthrough does not appear, debug the context before redesigning the page.
Drillthrough is not only filtering; it is navigation. Users should immediately know where they are, what entity is filtered, and how to return to the summary page.
A user who drills into 'Fire Prevention' should see that context in the page title, supporting KPIs and detail visuals — and should have an obvious route back.
[ Back ]
Department Detail: <selected department>
Top:
- Open Cases
- Avg Age
- Critical Count
Middle:
- Trend
- Status Breakdown
Bottom:
- Record-Level Table
- Owner / ID / Date / StatusA drillthrough page should feel like the natural next chapter of the story, not a disconnected report page.
Power BI supports drillthrough actions on buttons. This can make navigation more discoverable because users see a clear call to action instead of relying on a context menu.
If your audience rarely right-clicks charts, a visible 'View Department Details' button can make the report behavior obvious.
Source page:
1. User selects one Department
2. Button becomes relevant
3. Action = Drillthrough
4. Destination = Department Detail
Label:
"View Department Details" Use buttons when explicit navigation improves usability, but keep the underlying context rule just as strict.
Drillthrough can cross report boundaries in Power BI Service. This is useful when a summary report and a detail report are intentionally separated but share compatible context fields.
A citywide KPI report can drill into a dedicated operations report, as long as the target context is designed consistently and deployment requirements are met.
Source report + Target report
Required:
- Same workspace
- Matching drillthrough field name
- Matching data type
- Cross-report drillthrough enabled
- Target drillthrough page configured
- Publish / refresh both reportsUse cross-report drillthrough only when report separation improves architecture or ownership without making navigation confusing.
When drillthrough fails, the root cause is often context or model logic rather than the target page itself. Validate the field, the source visual, the relationships and the expected filtered rows.
If a Department Detail page shows 42 cases when the source KPI says 17, that is a data-model or filter-validation problem, not a navigation success.
1. Is target drillthrough field configured?
2. Is the field in source visual context?
3. Does the target page receive the expected value?
4. Do model relationships propagate that value correctly?
5. Are keys duplicated / transformed?
6. Do totals match trusted validation results?
7. If needed, inspect query behavior with Performance Analyzer.Treat drillthrough like any other analytical feature: validate the numbers, not just the navigation.
Drillthrough is strongest when it supports a predictable decision path: identify an issue, select the entity, inspect the evidence, then return to the summary with better understanding.
Do not create detail pages because Power BI can. Create them because users repeatedly ask the next question and need a focused place to answer it.
1. What summary question is the user answering?
2. What is the next detail question?
3. Which entity key carries the context?
4. Is that key in the source visual context?
5. Is the target page focused on detail?
6. Is Back navigation obvious?
7. Would a visible button improve discovery?
8. Are relationships/filter paths correct?
9. Do detail totals match trusted validation?
10. Is cross-report drillthrough really needed?
11. Have source and service behavior been tested?
12. Does the page reduce analysis friction?The goal is not more navigation. The goal is faster movement from a signal to the evidence behind it.
Open each item after answering it in your own words. The 24 interactive practices above drive certificate progress.
Drillthrough changes page and analytical depth; drill down stays inside the visual hierarchy.
Drillthrough filter fields define the target context.
The source context may not contain the target drillthrough field.
It makes the navigation action more visible and intentional.
Correct context and validated detail results prove the design.
| Layer | Purpose |
|---|---|
| Source Visual | Expose the entity in selection context |
| Drillthrough Field | Define the context passed to the target page |
| Target Page | Answer the next-level detail question |
| Back / Button | Make navigation obvious |
| Validation | Confirm rows, totals and filter propagation |
Complete at least 12 of the 24 practice cases (50%) and enter your name.
This training is aligned to current Microsoft Learn guidance for drillthrough in Power BI reports.