Skip to content
Tutorials Center
My learning

Topics

Lesson 22 of 38 ยท Model-driven Apps

Site Maps, Dashboards and Charts

Design navigation with the model-driven app site map, then add system and personal dashboards, charts and views so users see key numbers at a glance.

Once forms and views exist, users need a way to reach them and a place to see how things are going. In a model-driven app the site map provides navigation, and dashboards and charts provide the overview. This lesson covers how they are structured and how to design them well.

The site map

The navigation bar on the left of a model-driven app is its site map. It has a hierarchy:

  • Area: the top level (for example Sales, Service). Shown as a switcher at the bottom of the left pane in many layouts.
  • Group: a heading inside an area (for example Customers, Activities).
  • Subarea (page): a link to a table's views, a dashboard, a URL or a custom page.

In the app designer you edit this in the Navigation pane: choose Add, then Add page or Add group; drag items to reorder; select an item to set its Title, Icon and ID. You can also toggle Show recent and Show pinned, which lets people return to rows they used.

Design guidelines:

  • Keep to 2 to 3 groups with 3 to 6 pages each. A long list hides what matters.
  • Name pages with plain words your users use, not table names.
  • Put the most used page first.
  • Give each area a role: if sales and finance staff need different pages, create areas and use security roles to hide tables they cannot read.

Site map levels

Area Top level, e.g. Sales
Group A heading in an area
Page A table, dashboard or URL

Fewer, clearer links work best.

1 / 2

Representing a site map as data: a stand-in

A site map is a tree. This stand-in prints one and counts its links; the real definition is stored in the app's metadata.

JS Stand-in: render a site map tree

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Charts

A chart summarizes rows of one table. In the maker portal choose the table, then Charts, then New chart. You choose:

  • Chart type: column, bar, line, area, pie, donut, funnel or tag chart.
  • Category (the horizontal grouping, for example Status or Month).
  • Series (the value that is measured), with an aggregate: Count, Sum, Average, Min or Max.
  • Optionally a second series or a date grouping (day, week, month, quarter, year).

A chart is tied to a view: it shows the rows that view returns. In the grid, open the Show Chart pane and pick a chart, and click a bar to filter the grid to those rows.

Create the chart on a purpose-built view (for example "Open requests this quarter") rather than on the default view. That way the chart answers one clear question.

Dashboards

A dashboard places several components on one page:

  • Charts
  • Lists (a view of a table)
  • Iframes and web resources
  • Timeline and assistant panels in some apps

Two kinds exist. System dashboards are part of the solution and available to everyone with access. Personal dashboards belong to one user and can be shared. System dashboards can use layouts with one to four columns; you add components by selecting a layout cell and choosing the component type.

Dashboards in model-driven apps are a good fit for quick operational views. For deep analysis and cross-source reports, embed or link a Power BI report instead.

The logic behind a chart: a stand-in

A chart is a group-by with an aggregate. This stand-in computes "count and sum by status", the same idea behind a column chart.

JS Stand-in: group by and aggregate

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Putting it together

A typical delivery order for the UI layer:

  1. Build tables, columns and relationships.
  2. Create forms and views.
  3. Create two or three charts on those views.
  4. Add a dashboard for each main role.
  5. Arrange the site map around the dashboards and most used tables.
  6. Publish and test with a user who holds only the target role.

Test with the real role. A dashboard component the user cannot read shows an access error instead of data.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the correct site map hierarchy?

    A site map has areas that contain groups, which contain subareas (pages).
  2. 2. A chart in a model-driven app summarizes rows from...

    Charts are built on one table and use a view to select rows.
  3. 3. Which aggregate functions can a chart series use?

    Chart series use aggregates such as Count, Sum, Average, Minimum and Maximum.
  4. 4. A dashboard that everyone with app access should see is a...

    System dashboards are part of the solution; personal ones belong to a user.

Summary

  • The site map organizes areas, groups and pages; keep it short and named in user language.
  • Charts group and aggregate one table's rows via a view; dashboards combine charts, lists and more.
  • System dashboards are shared with the app; personal dashboards belong to a user.
  • Test navigation and dashboards with the actual security role.

Next: Connectors: The Big Picture