Guide section 30 of 31
Open Questions / Unresolved Areas
| Open question | Status / what remains |
|---|---|
| Exact current Power UI inventory and automation mechanism | The recovered work treats Power UI as an organization-specific standardization/configuration layer, but its exact current component set and PBIP/theme automation were not conclusively documented. |
| Power UI rollout vs pilot scope | Earlier work positioned Power UI as a pilot/implementation layer; production governance and ownership need an explicit internal decision. |
| Nudge BI licensing / shared-library rights | The guide noted that team sharing rights depend on the purchased license; verify before distributing assets broadly. |
| Automatic design-token pipeline | No evidence supports automatic synchronization from design tokens/Figma to Power BI. A controlled mapping is recommended; the degree of automation remains to be decided. |
| PBIP starter contents | The concept is agreed, but the exact starter repository structure, theme files, report skeleton, naming and CI/CD conventions were not fully recovered. |
| Preview features | Date-picker slicer mode, list slicer, Shape Map and any preview item should be revalidated before becoming a standard. |
| Custom visual approval process | The decision framework is clear, but the precise governance owner/security/performance checklist was not fully defined. |
| Print strategy | A4/PDF is a known requirement in some reports; decide when to use a dedicated interactive print page versus paginated reporting. |
| Embedded application-level filters | Prior context included application-level campaign/period filters spanning pages; the exact contract between app shell and report-level filters needs to be documented per embedded solution. |
| Performance budgets | Performance is a core principle, but no universal maximum visual/query budget was agreed; define measurable thresholds with the BI engineering team. |
| Naming/versioning/governance of patterns | The hierarchy is agreed; ownership, release/versioning and deprecation process for the reusable library still needs formalization. |