Create a model-driven app that has an account table page

Model-driven app design is a component-focused approach to app development. Model-driven apps are especially well suited for process driven apps that are data dense and make it easy for users to move between related records. For example, if you are building an app to manage a complex process, such as onboarding new employees, managing a sales process, or member relationships in an organization like a bank, a model-driven app is a great choice. Model-driven apps also allow you to quickly build an app by combining components like forms, views, charts, and dashboards.

In this tutorial, you create a model-driven app by using one of the standard tables that is available in Microsoft Dataverse, the account table.

Sign in to Power Apps

Sign in to Power Apps. If you don't already have a Power Apps account, select the Get started free link.

Select the environment

An environment in Power Apps is a space to store, manage, and share your organization’s business data, apps, chatbots, and flows. It also serves as a container to separate apps that might have different roles, security requirements, or target audiences.

Each environment can have one Dataverse database.

Select the environment you want, or go to the Power Platform admin center to create a new one. You can choose the environment by selecting Environment from the upper right.

Create your model-driven app

We recommend creating your model-driven app from a solution. A solution is a package that can contain Dataverse tables, forms, views, apps, flows, and other components. By building your model driven-app in a solution, you can easily move it to other environments or preserve a copy in your source control repository.

  1. Select Solutions on the left navigation pane, and then select New solution. More information: Create a solution.

  2. Enter a Display name for your solution, such as Power Apps Training. Next, you add the account table that will be included in your model-driven app.

  3. In your solution, select Add existing, and then select Table.

  4. Under Add existing tables screen, select the Account table, and then select Next.

  5. Select Include all components, and then select Add.

    Now that you have a solution and have added the account table to it, you're ready to create a model-driven app.

  6. In your solution, select New, select App, and then select Model-driven app.

  7. Select Modern app designer, and then select Create

    Use the modern app designer to create a model-driven app.

  8. Enter a name for the app, such as My new custom app2, and then select Create.

    Enter a name and then select Create.

Add pages to your app

Next, you add a new page to the model-driven app.

  1. Select New page from the Pages menu.

    Add a page to a model-driven app.

  2. Select Table based view and form, and then select Next.

    Select a table-based view and form.

  3. Select the Account table, and then select Add.

    Select the account table to add it to the app.

    The account form and view appear in the pages menu.

  4. Select Account view, and then select Manage views.

    Manage an account view.

  5. Select the following views: Active Accounts, All Accounts, My Active Accounts, Account Advanced Find, and Account Lookup, and then select Save.

    Select the views to add in the app.

  6. On the app designer command bar, select Save.

Publish your app

  1. On the app designer command bar, select Publish.

After publishing the app, it's ready for you to run or share with others.

Run your app on a desktop computer

  1. To run your app, sign in to Power Apps, and on the left navigation pane, select Apps.

    Select Apps.

  2. Select the app from the app list. The app opens in your browser.

    Simple account table app.

Run your app on mobile

To run your app on your mobile device, follow these steps:

  1. Download the app from your device's mobile app store:

  2. Open the app, tap Sign in, and then enter your Microsoft work or school account.

  3. Select your app from the list to run it.

See also

Overview of the model-driven app designer