Page pattern
Search / Explore
Find one record or a small set of records inside a large table and continue to its detail page.
- “Where is this article?”
- “Which items match these criteria?”
- “What is the value for this specific store?”
Search / Explore — clickable example
Shared retail dataset. Every control works; the log shows what Power BI would change.
Native slicer with search enabled; matches values, not free text.
| vs Budget | ||||
|---|---|---|---|---|
| Fresh | €2.4M | €2.5M | €608k | ▼ -0.9% |
| Beverages | €1.7M | €1.7M | €426k | ▼ -0.7% |
| Grocery | €1.7M | €1.7M | €426k | ▼ -0.8% |
| Non-food | €1.4M | €1.4M | €346k | ▼ -1.4% |
| Household | €1.2M | €1.2M | €291k | ▼ -1.7% |
| Total | €8.4M | €8.5M | €2.1M | -1.0% |
- Interact with a slicer, a bar or a navigation button to see the native behaviour described here.
Search / Lookup — archetype wireframe
[ Search / filter area ] [ Result count / context ] [ Results table ] [ Selection / actions ]
Reading order follows the zones above, top-left to bottom-right.
Components: Slicers, Text/search slicer patterns, Table, Matrix, Buttons
Hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
Interaction: Use only interactions that support the page's next analytical step; typical next level: **Entity detail**.
Navigation: Entity detail
Implementation: Compose from the listed native visuals/controls and the standard interaction patterns in this guide; custom visuals are exceptions.