Charts, dashboards, and views in Dataverse

The day-to-day analytical surface in model-driven Power Apps and Dynamics 365 CRM-side apps comes from three components: views, charts, and dashboards. Each has its place; understanding the layered configuration is essential to giving users useful surfaces without proliferating noise.

Views. A view is a filtered, sorted, columnated list of records on a single table. Each table has:

• System views — provided by Microsoft (All Active Accounts, My Active Opportunities, Closed Cases This Month). Maintained by the platform; customers can edit but not delete.
• Custom views — created by admins / system customisers. Saved at the table level; available to all users with permission.
• Personal views — created by individual users from the user interface. Visible only to the creator, optionally shareable.

A view defines:

• Filter criteria — which records to show.
• Columns — what fields to display, in what order, with what width.
• Sort order — default sort.
• Result limits / paging — usually inherited from platform defaults.

View types.

• Public — visible to everyone with table access.
• Personal — owner-scoped, optionally shared with teams.
• Quick Find — special view defining searchable columns (see the Dataverse search guide).
• Advanced Find — special view for ad-hoc filtering UX.
• Associated — special view for related-record subgrids.
• Lookup — special view for lookup pickers.

Each table has one of each special type; customisation tunes them.

Charts. Charts are visualisations bound to a view:

• System charts — table-level; show data from the current view, automatically updating as the user picks different views.
• Personal charts — user-created, visible only to the creator.

Chart types include bar, column, line, pie, doughnut, area, funnel. Configuration: choose which fields are the axis, which are the values, optional grouping, and the colour scheme.

Charts render inline on list pages — the user sees the chart above the list, both filtered by the current view. Drilling down on the chart filters the list to the slice clicked.

Dashboards. A dashboard is a multi-component composition of charts, lists, web resources, and Power BI tiles. Each table can have its own dashboards; cross-table dashboards exist at the app level.

Dashboard types:

• System dashboard — admin-configured, available to all users with the role.
• Personal dashboard — user-created, visible only to creator.
• Interactive dashboard — modern, with persistent filters and global streams; tuned for case-management-style work where the user filters and processes records inline.

Power BI integration. Beyond native Dataverse charts, Power BI tiles can be embedded in dashboards:

• Power BI dashboard tile — a tile from a Power BI dashboard.
• Power BI report tile — a full Power BI report embedded.

For complex analytical surfaces, Power BI is the better tool than native Dataverse charts. The integration gives users a single dashboard surface combining operational data (Dataverse views) and analytical data (Power BI).

Designing for users.

• Per-role dashboards — different defaults for sellers vs service agents vs managers.
• Limit dashboard count — 5–10 well-curated dashboards beat 50 stale ones.
• Refresh expectations — Dataverse charts are real-time; Power BI tiles refresh on their own schedule (typically not real-time).
• Mobile dashboards — different rendering; design with mobile in mind.

Common patterns.

• Manager dashboards — team pipeline, team performance, exceptions.
• Agent dashboards — open cases, SLAs at risk, recent activities.
• Executive dashboards — high-level KPIs, often Power BI-driven.
• Operational dashboards — daily-glance views for specific roles.

Operational discipline.

• Govern personal-view sharing — personal views shared too widely become semi-system views with no governance.
• Retire stale dashboards — dashboards nobody uses are clutter. Audit annually.
• Test refresh frequency — users complaining that "the dashboard is wrong" usually means stale data from misunderstood refresh cadence.

Where Dataverse charts fall short. Complex analytical needs — multi-table joins, complex calculations, sophisticated visualisations — outgrow Dataverse charts. Move to Power BI. Native charts cover the operational "what's happening on my team today" question; analytical depth belongs in Power BI.