Power BI drillthrough: from a summary number to its detail page
Power BI drillthrough lets a reader jump from a summary visual to a page of detail about one item. Someone sees a weak month for a customer, right-clicks the bar and lands on a page filtered to that customer alone. So the overview stays uncluttered, while the detail sits one click away. This guide explains how the feature works, how to set it up and where designers slip.
- Summary first, detail on demand
- Four setup steps
- Related features compared
Last updated
Power BI drillthrough: what is it?
It is a way to link report pages through the data itself. An author designs a detail page about one entity, such as a customer, a product or a store. Then any visual that uses that entity can send a reader there.
The reader right-clicks a data point and chooses the detail page from a menu. The page opens with a filter for the item they clicked. As a result, one page design serves every customer, product or store in the model.
This keeps reports lean. Instead of cramming every column onto the overview, the author shows a few key figures first. Readers who want more then ask for it, and everyone else sees a clean page.
How to set up a detail page in four steps
The setup happens in Desktop, and it takes only a few minutes once the detail page exists.
Design the target page
First build a page that makes sense for a single item, with a title that shows which item the reader chose.
Add the field
Then drag the entity field, such as customer name, into the drill through area of the Visualizations pane.
Check the back button
Next confirm that Desktop added a back button, and move it somewhere obvious, because readers need a way to return.
Test from a source visual
Finally, go to another page, right-click a data point that uses the field and follow the menu to the target.
How does a Power BI drillthrough page receive its filters?
The target page receives a filter on the field you placed in the drill through area. When a reader clicks one customer, that customer becomes the filter. So every visual on the target page shows that customer only.
Other filters can travel too. A setting named Keep all filters controls this. When it is on, the target page also inherits the rest of the context from the source visual, such as the year or region in effect. When it is off, only the chosen field passes.
Designers should decide this deliberately. A reader who filtered to one year usually expects the detail page to respect it. However, a detail page meant to show full history may work better with only the entity filter.
Drill down, tooltips and detail pages: which does what?
Several features sound alike, so this table sets them side by side.
| Feature | What the reader does | Best for |
|---|---|---|
| Drillthrough | Right-clicks a data point and opens a target page | Full detail about one item |
| Drill down | Moves one level down inside one visual | Hierarchies such as year to month |
| Report page tooltip | Hovers to see a small custom page | A quick look without leaving the page |
| Cross-report drillthrough | Jumps to a target page in another report | Shared detail pages across reports |
| Drillthrough button | Selects a data point, then clicks a button | Readers who do not right-click |
Power BI drillthrough mistakes that confuse readers
The first mistake is a hidden feature. Many readers never right-click, so they never find the detail page. A short hint near the visual helps, and a button makes the path visible.
The second mistake is a target page with no context. When the page opens without a title that names the item, readers cannot tell what they are looking at. Therefore add a card or a dynamic title that shows the current selection.
The third mistake is leaving the target page in the normal page tabs. Someone who opens it directly sees unfiltered totals that look wrong. So most designers hide the page, and readers reach it only through the intended route. Also, test the back button after every layout change.
Power BI drillthrough questions from report designers
Can the feature work across two reports?
Yes. Microsoft documents cross-report drillthrough, which sends a reader from one report to a target page in another. Both reports need the option turned on, and the field names must match. Conditions on workspaces apply as well, so check the current documentation before you design around it.
Why does the option not appear on right-click?
Usually because the source visual does not use the field that the target page expects. The menu appears only when the clicked data point carries that field. First confirm that both pages use the same column from the same table. Then check the field's settings on the target page.
Does Power BI drillthrough keep the slicer selections?
It can. With Keep all filters switched on, the target page inherits the filters that affected the source data point, including slicer choices. With it off, only the drill field passes. Try both settings with real readers, since the better choice depends on what they expect to see.
Can a button trigger the jump instead?
Yes. A button can carry a drill through action that points at a target page. It stays inactive until the reader selects a single data point, and then it lights up. Because the button is visible on the page, more readers discover the detail than with a right-click menu alone.
Can Power BI Agency redesign our detail pages?
Yes. One of our consultants reviews how readers move through your reports, then rebuilds the summary and detail pages to match. The work takes place online inside your own tenant, with a weekly demo. We are a division of Sataware Technologies and independent of Microsoft. Start with the free 30-minute assessment.
Let's build your first dashboard together.
Tell us what you report on today. A consultant replies within 2 hours with next steps.
Trusted partners
Microsoft Solutions Partner · AWS Partner
Cloud & AI Platforms
Azure SQL, Microsoft Fabric and the data pipelines behind your reports.
AI Business Solutions
Power BI reporting on your Dynamics 365, Business Central and Power Platform data.
Security
Row-level security and Entra ID sign-in on every report and workspace.
Amazon Web Services
Power BI on your AWS data, with connectors for Redshift, Athena and S3.