Guide section 45 of 55
Components should often become configurations
Instead of designing a custom "Enterprise Data Table Component", define *our approved configuration of the native Power BI Table*:
| Property | Approved configuration |
|---|---|
| Header | 14 px / semibold |
| Rows | Compact density |
| Numeric columns | Right aligned |
| Text columns | Left aligned |
| Default sorting | Task-dependent, always specified |
| Conditional formatting | Semantic status only |
| Drillthrough | Row / selected entity |
| Empty state | Defined |
| Export | Enabled where permitted |
The same principle applies to Matrix, KPI cards, slicers, filter bars, navigation and comparison charts. This is far more maintainable than recreating a frontend component library inside Power BI.