How to build Model-driven App in Power Apps - Part I

Table of Content:

• Introduction to Microsoft Dataverse
• Introduction to model-driven apps
• Microsoft Dataverse and model-driven apps working together
• Explore sample template apps
• Summary

Introduction to Microsoft Dataverse

Whether you are building a canvas app or a model-driven app, Dataverse is the ideal data source because it is the foundational data source of Microsoft Power Platform. As a result, you will experience the most functionality, the deepest integrations, the most features, and the best ease of use of any available data sources. From simple web-based data design to robust, role-based security, Microsoft Dataverse is a straightforward platform that you can use to begin designing your data structures and helping to keep them safe. Then, with your data in place, you have rich integration capabilities from Power Apps and the rest of Microsoft Power Platform. Additionally, by applying business rules, you can trust that your business integrity will be maintained no matter what tool you use to interact with the data.

Another benefit of using Dataverse is that all of your data is stored in tables. A table is a set of records that are used to store data, similar to how a table stores data within a database. Dataverse includes a base set of standard tables that cover typical scenarios, but you can also create custom tables that are specific to your organization. Standard and custom tables within Dataverse help provide a secure and cloud-based storage option for your data. Tables allow you to create a business-focused definition of your organization's data for use within apps.

Some benefits of using Dataverse and its tables include:

• Simple to manage?- Both the metadata and data are stored in the cloud so that you're confident about the details of how they're stored.
• Helps secure your data?- Data is stored so that users can see it only if you grant them access. Role-based security allows you to control access to tables for different users within your organization.
• Access your Dynamics 365 data?- If you use Dynamics 365, data from your Dynamics 365 application is also stored within Dataverse, allowing you to quickly build apps that use your Dynamics 365 data and extend your apps by using Power Apps.
• Rich metadata?- Data types and relationships are used directly within Power Apps.
• Logic and validation?- Define calculated columns, business rules, workflows, and business process flows to ensure data quality and drive business processes.
• Productivity tools?- Tables are available within the add-ins for Microsoft Excel to increase productivity and ensure data accessibility.

Now that you have a better understanding of how Dataverse works and are aware of some of the benefits, you can now explore how these benefits can be applied in a model-driven app.

Introduction to model-driven apps

Unlike canvas apps, where you build out an app screen-by-screen by adding logic and code as you go, model-driven apps can be created with a few simple steps. Model-driven apps use a component-focused approach to develop the app. When developing canvas apps, you have complete control over the appearance and behavior of your app, whereas, with model-driven apps, the layout is mainly based on the components that you add to the app.

With model-driven apps, a number of different components and component properties are available for you to add and modify when designing an app.

Model-driven app design provides the following benefits:

• Rich component-focused, no-code design environments
• An ability to create complex responsive apps with a similar UI across a variety of devices from desktop to mobile
• Robust design capability
• Apps can be distributed as a solution

Microsoft Dataverse and model-driven apps working together

When creating a model-driven app, you can use tables from Microsoft Dataverse as your building blocks. Model-driven apps?start with your data model, building up from the shape of your core business data and processes in Dataverse to model forms, views, and other components.

It's important to ensure that your business data and business processes at the data level are structured properly before you compose your app. Model-driven apps will automatically generate a UI that is responsive across devices; however, this outcome relies heavily on how your data is modeled in Dataverse.

Approach to model-driven app making

When creating model-driven apps, it's important to focus on three areas:

• Modeling business data
• Defining business processes
• Composing the app.

More information on creating model-driven apps is included in the Create relationships, business rules, calculations, and rollups in Dataverse Learning Path and in?Overview of building model-driven apps.

Explore sample template apps

In?Power Apps, you can use a sample app to explore design possibilities. You'll also discover concepts that you can apply as you develop your own apps. Every sample app uses fictitious data to showcase a real-world scenario.

For more details, be sure to check out the documentation that's specific to each sample app.

Get sample apps

Before you can experiment with or edit the model-driven sample apps, you must set them up in a Microsoft Dataverse database. If you have not already created a trial environment, follow the steps in the?Create a trial (standard) environment in the Power Platform admin center?learning module. Make sure that you select the?Deploy sample apps and data?toggle.

In Power Apps, select the environment you want, or go to the?Microsoft Power Platform admin center?to create a new one. Select?New, provide a name,?Yes?to Create a database for this environment, and select?Save.

Important - By selecting the?Deploy sample apps and data?toggle, you will install all available sample apps in your database. Sample apps are for educational and demonstration purposes. We don't recommend installing them in production databases.

Run a sample app

To run a sample app, follow these steps:

• Sign in to?Power Apps?to see a list of available sample apps. For this example, select?Fundraiser.

• At the top of the page, select?Show Visual Filter?to show graphs and charts where you can see how donations to fundraisers are performing. In the next steps, you'll create a new fundraiser and submit a donation to that fundraiser.
• On the left pane, under?Fundraiser, select?Fundraisers.
• Select?+ New?to add a new fundraiser.
• Under the?General?tab, enter the following information: Name?- My Fundraiser
• In the upper-right corner, select the drop-down arrow next to?Total Donations.
• From the drop-down menu, enter the following information: Fundraiser Goal?- 500
• On your keyboard, press?Enter.
• Select?Save & Close.
• On the left pane, under?Fundraiser, select?Donations.
• Select the drop-down arrow to the right of?Other Activities.
• From the drop-down menu, select?Donation.
• Enter the following information:

- Subject?- My First Donation

- Donation Amount?- 100

- From?- Nancy Anderson (sample)

- Regarding?- My fundraiser

Select?Save & Close.

On the left, select?Dashboards.

Select?Show Visual Filter.

Notice?Total Donations vs Goal by Fundraiser?shows your donation.

You have successfully run a sample model-driven app, added a new fundraiser, and added a donation to the fundraiser. While this is a quick look at an app and the related pieces, there is much more to learn about creating an app.

Summary

The goal of this module was to help you become familiar with the basics of Microsoft Dataverse and create model-driven apps. Dataverse lets you store and manage data that is used by business applications. Tables within Dataverse are used to store data.

To review, this module explained the following concepts:

• Dataverse data is stored in tables.
• You can use as many default tables as possible to quickly build apps.
• You can create new tables.
• Data is stored in a way that users can see it only if you grant them access.
• Sample apps and templates are available to help you learn and create your own apps

This article is part of Microsoft Certified: Power Platform App Maker Associate and will be one of many in the series of articles on my journey to become a Microsoft Power Platform Architect:

1. PL – 900 – Power Platform Fundamentals
2. PL – 100 - Microsoft Power Platform App Maker
3. PL – 200 - Microsoft Power Platform Functional Consultant
4. PL – 400 - Microsoft Power Platform Developer
5. PL – 600 - Microsoft Power Platform Solution Architect

Until next time,

Nikola Basta