Dashboard Framework Insights

Updated Summary (Including Required Subscriptions)

• Dashboard purpose clarified — You are designing a multi‑layer financial dashboard with strict separation of actuals, logic, scenarios, and simulated outputs.

• Layer 1 definition corrected — Layer 1 includes:

  • Actual ratios

  • Summary graph by periods

  • Current‑month financial snapshot

  • High‑level signals

• Need for detail access without clutter — The main dashboard must remain clean while still allowing drill‑down access to detailed logic.

• Two‑layer model established initially — Layer 1 = Actuals Summary Layer 2 = Actual Logic

• Scenarios require separation — Scenario simulations cannot mix with actuals or logic.

• Layer 3 introduced as scenario engine — Controls only: case selector, assumption overrides, variable toggles.

• Simulated results need a home — Layer 3 cannot display outputs because it is a control layer.

• Layer 4 introduced for simulation outputs — Layer 4 = Simulation Output Dashboard (simulated ratios, totals, comparisons).

• Final 4‑layer architecture defined — Layer 1: Actuals Summary Layer 2: Actual Logic Layer 3: Scenario Engine Layer 4: Simulation Outputs

Updated Subscription Requirements (Added to Summary)

• Dataverse requires a Business Microsoft 365 tenant — Microsoft 365 Personal cannot access Dataverse. You must switch to a Business plan (e.g., Business Basic).

• Dataverse requires a Power Apps license — Power BI alone does not unlock Dataverse. You need either:

  • Power Apps Per App (cheapest)

  • Power Apps Per User (full access)

• Power BI Pro required for publishing dashboards — Needed to publish and share your dashboards online.

• Recommended subscription stack for your dashboard —

  • Microsoft 365 Business Basic (to access Dataverse)

  • Power Apps Per App (to unlock Dataverse tables)

  • Power BI Pro (to publish dashboards)

This is the minimum viable, lowest‑cost, fully functional setup for your 4‑layer architecture.