Guide section 20 of 31
Native vs Custom Decision Framework
Use the lowest-complexity layer that satisfies the analytical requirement.
1. Native Power BI visual / control
↓ if insufficient
2. Native + formatting / DAX / conditional formatting / analytics / interactions
↓ if insufficient
3. Approved reusable Power UI configuration / pattern
↓ if insufficient
4. Deneb or another approved custom visual
↓ if insufficient and business value justifies it
5. Custom embedded development outside normal report composition| Layer | Use when | Governance position |
|---|---|---|
| Native Power BI | Meets analytical question with acceptable UX. | Default. |
| Native + configuration | Native visual works with theme/formatting/DAX/parameters/bookmarks/conditional formatting. | Preferred before custom. |
| Nudge BI | Design/prototype representation in Figma. | Design aid only; always map to runtime component. |
| Power UI | Organization standardization/configuration where available. | Use to reduce manual setup; does not create new runtime capability. |
| Deneb | Precise/custom data visualization not met by native visuals. | Exception; validate maintainability, skills, accessibility, performance and export. |
| Other custom visual | Specialized need with approved visual. | Exception; require governance and lifecycle review. |
| Custom embedded development | Requirement is genuinely application behavior beyond report runtime. | Last resort; separate product/engineering decision. |