Page pattern

Drillthrough Detail

A dedicated destination page reached by right-click, filtered to exactly the point the user selected.

DetailBasicArchetype: Transaction Detail

Typical user questions

Shared retail dataset. Every control works; the log shows what Power BI would change.

Simulation of native Power BI behaviour

Filter contextDepartment:All

Applied drillthrough filters + backcontext

OverviewAll departmentsWeeks:1–13

Context KPIskpi

Revenue€8.4Mvs Budget€8.5M▼ -1%Attention

vs Previous year€8.4Mvs Previous year€8.3M▲ +1.4%On track

Margin€2.1Mvs Benchmark€2.1M▼ -0.2%Attention

Record tabledetail

Supporting contextsupporting

What Power BI would do

Interact with a slicer, a bar or a navigation button to see the native behaviour described here.

[ Context ] [ Summary ] [ Transaction table ] [ Supporting metrics ]

Simulation of native Power BI behaviour

Zone 1

Context

Zone 2

Summary

Zone 3

Transaction table

Zone 4

Supporting metrics

Reading order follows the zones above, top-left to bottom-right.

Designer

Components: Table, Matrix, Cards, Slicers

Hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.

Developer

Interaction: Use only interactions that support the page's next analytical step; typical next level: **Back to analysis**.

Navigation: Back to analysis

Implementation: Compose from the listed native visuals/controls and the standard interaction patterns in this guide; custom visuals are exceptions.

Common mistakes

Treating the archetype as a rigid screen; adding unrelated analytical tasks; duplicating controls already handled globally.