← All entries

Adding system dashboards to a model-driven app

Praxisis D365 Wiki · Public reference · Client-specific details redacted

Source: Claude.ai chat (original: system-dashboards-display__c10d6131.md) Added: 2026-10-02

Summary

  • A new system dashboard is not auto-added to existing apps. Open the solution → app designer → Pages → + Add page → Dashboard → tick the dashboard → Save + Publish the APP (not just the dashboard).
  • Users must hard-refresh (Ctrl+F5). Showing "Dashboards" in the sitemap requires leaving Show in navigation ticked.
  • Why a dashboard still won't appear: not in app components · not published · role-restricted via Enable Security Roles · user missing table privileges on referenced charts/views · no sitemap subarea of type Dashboard.

Key takeaways

  • Promoting to UAT/Prod: in the solution use Add existing → Dashboard (and include the AppModule + sitemap in the same solution package) — otherwise the app will reference a missing component.
  • Repo / PAC CLI route: dashboards unpack as systemform records with form type 0 under Dashboards/. In AppModule.xml add <AppModuleComponent type="60" id="{DASHBOARD_FORM_GUID}" /> (type 60 = SystemForm). In the sitemap XML, ensure a Dashboards subarea exists; optionally pin DefaultDashboard="{GUID}".
  • Tip: build the first dashboard in the UI, then pull — the generated XML is the exact pattern to copy for the rest.

Learnings / how to apply

  • "Dashboard not appearing" is a top-5 support ticket pattern — fold the 5-reason checklist into the Praxisis Sustain Operating Model's model-driven-app troubleshooting runbook.
  • For repo-managed solutions, document the type-60 AppModuleComponent pattern + sitemap pairing so new consultants can promote dashboards without the UI round-trip.

Need this applied to your own tenant?

Praxisis Sustain Self-Serve builds a private AI Wiki trained on your documents and tickets, with free Tier-2 support when the AI cannot answer. Book a 30-min overview.