Power BI Drillthrough - The Most Underused Feature for Cleaner Reports

I want to talk about drillthrough. It's one of those Power BI features that's been around forever, sits in the middle of the Microsoft documentation, and gets ignored by maybe two thirds of the report builders I work with. Which is a shame, because it's the single most effective tool for the "summary on one page, detail on another" pattern that almost every business report eventually needs.

The pattern is straightforward. You have a sales dashboard that shows revenue by region. A regional manager wants to click on Queensland and see the underlying detail: which customers, which products, which deals. Without drillthrough, you either cram all that detail onto the summary page (where it sits ignored because everyone wants the headline), or you build a separate detail page and force the user to apply their own filters (which they won't). With drillthrough, the user right-clicks the bar for Queensland, picks the detail page from a menu, and lands there filtered. One click. No fiddling with slicers.

That's the whole feature in two sentences. The hard part is using it well.

How drillthrough actually works

You build a destination page like any other. You then drag a field, say Region, into the "Drill through" well in the Visualisations pane. From that moment, any visual in the report that has the Region field becomes a drillthrough source for that page. Right-click any data point on those visuals, and Power BI offers to drill through to the destination, passing the region value as a filter.

You can pile up multiple drillthrough fields on a destination page. You can drill through to a page that filters by both Region and Product Category, for example. Right-clicking a stacked bar with both as dimensions will pass both into the destination.

The back button is added for you when you build the page. It uses bookmarks under the hood to remember which page the user came from. It works most of the time. It occasionally forgets where you came from if you've been bouncing around and the navigation stack gets weird, but that's rare enough not to worry about.

Cross-report drillthrough was added a few years back and is genuinely useful for shops with a sprawling estate of reports. You can drill from a sales report into a separate operational report, with the filter context carried across. We've used this a few times to stitch together a "company overview" view that drills into specialist reports owned by different teams.

The patterns that work well in practice

We use drillthrough for three main jobs in the reports we ship.

Summary to detail. The classic. A headline page showing sales by region, customer, or product. Right-click any of those entities and drill to a detail page filtered to that entity. The detail page might be a list of transactions, an account history, a customer profile. The user never has to think about filtering. The context follows them.

Master to anomaly. A KPI page that flags exceptions. Right-click an outlier, drill to a forensic page that explains why. We build this a lot for finance teams who want to investigate variances without leaving the report.

Entity profile. A customer 360 or product 360 page that gets used in dozens of contexts. Build it once as a drillthrough destination, then any chart anywhere in the report that uses the customer or product field becomes an entry point. This is the highest-value pattern. You can reuse a single well-built detail page from any summary visual that references that dimension.

We push this on every Power BI engagement because it's such a quick win. The amount of work to set up drillthrough on a single page is maybe thirty minutes. The improvement in usability is enormous. Compared to building dedicated detail pages for every entity and wiring up custom navigation, drillthrough is so much cheaper for the same outcome.

The bits that go wrong

Drillthrough is not perfect. A few things consistently catch people out.

The discoverability problem. Right-click is not an obvious gesture. Users on iPad or on Surface devices with touch don't get it. Even seasoned desktop users don't always think to right-click on a chart. The fix is to add a button visual on the summary page that explicitly triggers drillthrough using the drillthrough action. Or to add a tooltip that mentions "right-click to drill through to detail". Some sort of signpost, otherwise the feature stays hidden.

The "what page am I on" problem. Once you drill through, the user is on a new page with a filter applied from the source. If the destination page also has slicers, the interaction between the passed filter and the slicer state can be confusing. A user who later changes the slicer might not realise the underlying drillthrough filter is still active. We tend to add a small text element at the top of every drillthrough page that reads "Currently showing: Queensland" or similar, so the active drillthrough filter is visible. It's a tiny touch that prevents a lot of confusion.

The cross-report drillthrough discovery. The user has to right-click and find the cross-report option, which is buried in a submenu. Again, button visuals help. Or build entry points into the navigation as buttons that trigger drillthrough directly.

Mixing drillthrough with page navigation. If you have both right-click drillthrough and on-page navigation buttons that also pass filters, users end up with two ways to get to the same place, which is confusing. Pick a primary pattern. We tend to use drillthrough for "from a visual to detail about that visual" and use buttons for "from anywhere on the page to a fixed destination". The two don't overlap.

For our Power BI consulting work, drillthrough is one of the first things we audit when we inherit a report estate. Half the time, we find pages that are duplicates of each other with hard-coded filters, when one drillthrough destination would do the job of all of them.

Some things still missing

A few capabilities we'd like that aren't there yet.

You can't pass arbitrary URL parameters as part of a drillthrough action. If you want a drillthrough that lands on a particular slicer combination beyond what the source field gives you, you have to build that with bookmarks instead, and then drill through to a bookmarked state. It works, but it's a workaround.

There's still no way to define a drillthrough that pulls only some of the visuals on the destination page. The destination page is the destination page. If you want a "compact" version of the same detail, you build a separate page. Field parameters help a bit with this, but you can't dynamically choose the layout based on the entry point.

The mobile experience for drillthrough is rough. The right-click gesture maps poorly to touch. If you're shipping a report that will be consumed primarily on tablets, you'll need to design drillthrough entry points as buttons rather than relying on the right-click gesture. The Microsoft mobile experience for Power BI is generally not as polished as the desktop one, which is something we factor into early conversations on any business intelligence project.

The lever you should pull first

If you've got a Power BI report estate where everyone complains that the reports are "too big" or "have too many pages", the first lever to pull is drillthrough. Half those pages are probably duplicates with different filters. Collapse them. One summary page, a small number of well-built drillthrough destinations, and you've got a tighter, more usable report that's also far easier to maintain. We do this on basically every estate audit we run.

If you'd like a hand reviewing a report estate, or just want a second opinion on whether drillthrough is the right pattern for what you're building, get in touch. The original Microsoft reference is here: Use drillthrough in Power BI Desktop.