Skip to content
Tutorials Center
My learning

Topics

Lesson 19 of 38 ยท Model-driven Apps

Model-driven Apps - The Big Picture

Understand model-driven Power Apps: how tables, forms, views and a site map generate the interface for you, and when to choose them over a canvas app.

A canvas app starts from a blank screen: you place every control yourself. A model-driven app starts from your data. You describe the tables, the columns, the relationships and the business rules in Microsoft Dataverse, and the platform generates a responsive interface from that description. You still choose what appears, but you do not draw it pixel by pixel.

This lesson explains what a model-driven app is made of, how it differs from a canvas app, and how to decide between them. The product itself cannot run on this site, so we describe the designer's menus and settings precisely and use small, clearly labelled JavaScript stand-ins to show the ideas.

Menu names and layouts change as Microsoft updates the maker portal (make.powerapps.com). The concepts below are stable; if a label differs on your screen, look for the closest equivalent.

What a model-driven app contains

A model-driven app is a collection of components that you pick from your environment:

  • Tables (and their columns and relationships) that hold the data.
  • Forms that show or edit one row.
  • Views that list many rows with chosen columns, filters and sort order.
  • Dashboards and charts that summarize data.
  • Commands (buttons on a command bar) and business rules that add logic.
  • A site map (navigation) that groups these into areas, groups and subareas.

You assemble them in the app designer. Open make.powerapps.com, choose Apps, then New app, then Model-driven app (the wording is close to "Start with a blank page" or "Use the app designer"). Add pages, choose the table for each page, and save and publish.

Model-driven app parts

Tables Your data lives in Dataverse
Forms Edit one row
Views List many rows
Site map Navigation

The app designer only picks and arranges these parts.

1 / 3

Model-driven versus canvas

Question Canvas app Model-driven app
Where do you start? A blank screen The data model
Layout control Total, down to pixels Limited to forms, views, dashboards
Data sources Hundreds of connectors Dataverse tables (virtual tables can bring in others)
Business logic Power Fx formulas Business rules, plug-ins, flows, Power Fx commands
Best for Task apps, field tools, custom looks Case management, CRM-like and back-office apps
Responsive layout You build it Built in

Many solutions use both: a model-driven app for staff who manage records, and a canvas app for a mobile worker who does one task quickly. Both can sit on the same Dataverse tables.

How the generated UI comes from metadata

The key idea is that the interface is metadata-driven. The platform reads a description of the table and draws controls from it. Here is a stand-in that mimics that: it takes a table definition and produces a form layout. It is an illustration, not Microsoft's code.

JS Stand-in: a form generated from a table definition

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

No output.

Change a column's type and the generated control changes with it. In the real product you pick the column type when you create the column, and every form, view and chart respects it.

A simple decision helper

Choosing the app type is a design decision with a few clear signals. This stand-in scores a project description.

JS Stand-in: canvas or model-driven?

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

No output.

The weights are our own teaching heuristic, not an official rule. Use them to start a conversation, not to end one.

Building your first model-driven app

  1. In a solution (see Solutions and Environments), choose New, then App, then Model-driven app.
  2. Name it and add a page: choose Dataverse table, then pick one or more tables.
  3. For each table the designer adds its default views and forms. You can narrow these in the page settings.
  4. Arrange the navigation (see Site Maps, Dashboards and Charts).
  5. Save, then Publish, then Play to try the app in a browser tab.
  6. Share it with a security role (see Security Roles and Sharing). People see the app only if a role they hold grants access to it.

Common mistake: sharing the app but not giving the user a role with read privilege on the tables. The app opens, but the lists are empty or an access error appears.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What drives the interface of a model-driven app?

    The UI is generated from table metadata plus the forms, views and navigation you choose.
  2. 2. Which situation points most clearly to a model-driven app?

    Many related tables, security roles and heavy data entry are the model-driven sweet spot.
  3. 3. Which component groups the pages of a model-driven app for navigation?

    The site map (navigation) arranges areas, groups and subareas.
  4. 4. Why might a shared user still see no records?

    Sharing gives access to the app; table privileges come from security roles.

Summary

  • A model-driven app is generated from Dataverse metadata plus forms, views, dashboards, commands and a site map.
  • It suits complex, relational, security-heavy business apps; canvas apps suit custom, task-focused screens.
  • You build it in the app designer, then publish and share through security roles.
  • Both app types can share the same Dataverse tables.

Next: Forms, Views and Columns