Guide section 8 of 31
Table & Matrix Standard
The reusable standard should be a configuration of native Table and Matrix, not a new custom table control.
Table
Use Table for flat detailed records where users need exact values, sorting, scanning, conditional formatting, links/images where supported, tooltips, cross-filtering, export and scrolling.
Matrix
Use Matrix for hierarchical or multidimensional analysis: row/column hierarchies, drill, expand/collapse, stepped layout, subtotals/grand totals and conditional formatting.
| Topic | Standard |
|---|---|
| Hierarchy | Table: flat. Matrix: explicit hierarchy levels; show current depth and expand/collapse affordance. |
| Sorting | Set a task-oriented default: rank, chronology or business order. Do not rely on accidental source order. |
| Totals/subtotals | Use only when meaningful; visually differentiate without overpowering detail. |
| Row headers | Keep labels concise and readable; preserve hierarchy indentation where used. |
| Expandable hierarchies | Prefer Matrix when expand/collapse is part of the task; avoid simulating it in separate card rows. |
| Conditional formatting | Use semantic color, icons or data bars to aid scanning; always retain a textual/numeric cue. |
| Data bars | Useful for magnitude comparison in dense tables; ensure the numeric value remains readable. |
| Icons | Use as redundant status cues, not as the only carrier of meaning. |
| Sparklines | Useful as compact trend context when supported/governed; do not overload a wide table. |
| Drill | Specify whether hierarchy drill is allowed and what the default level is. |
| Column alignment | Text left; numeric columns usually right; headers aligned consistently with content. |
| Column sizing | Prioritize key columns; avoid forcing all columns into one viewport if readability collapses. |
| Numeric formatting | Standardize currency, percentages, percentage points, decimal places and abbreviations. |
| Scrolling | Treat scrolling as normal native behavior; avoid nested page/visual scroll where it harms orientation. |
| Pagination/virtual scrolling | Do not design a web-style pager unless the chosen Power BI mechanism actually provides it; test large-result behavior in runtime. |
| Empty states | Explain no-data vs no-results-after-filter; provide a recovery path such as clearing filters. |
| Selected states | Selection must be visible and its cross-filter/highlight consequence predictable. |
| Comparison columns | Group current/target/previous/variance logically and keep the comparison basis explicit. |
| Variance | Use sign, unit and semantic status consistently; distinguish % from percentage points. |
| Accessibility | Use clear headers, logical reading/tab order, non-color cues and consistent formatting. |
Recommended reusable variants
- Detail table — flat records, sortable, compact density, clear primary identifier.
- Comparison table — actual + target/budget + variance + status.
- Exception table — prioritized records with severity/reason and drillthrough.
- Hierarchy matrix — expandable organizational/product hierarchy with subtotals.
- KPI matrix — measures across entities/periods with controlled conditional formatting.
- Trend-in-table variant — compact sparkline only when it improves scanning and remains performant.