What is Logic
The logic components determine what business processes, rules, and automation the app has. Microsoft Power Apps makers use a designer that is specific to the type of process or rule they need.Expand table
| Type of logic | Description |
|---|---|
| Business process flow | Business process flows walk users through a standard business process. Use a business process flow if you want everyone to handle customer service requests the same way. Or you can use a business process flow to require staff to gain approval for an invoice before submitting an order. |
| Business rule | Business rules apply rules or recommendation logic to a form to set field requirements, hide or show fields, validate data, and more. App designers use a simple interface to implement and maintain fast-changing and commonly used rules. |
| Flows | Power Automate is a cloud-based service that lets you create automated workflows between apps and services to get notifications, sync files, collect data, and more. |
Visualization
The visualization components determine what type of data and reporting the app shows and which designer is used to create or edit that component.Expand table
| Component | Description |
|---|---|
| Chart | Charts are individual graphical visualizations that can appear in a view or a form or that can be added to a dashboard. |
| Dashboard | Dashboards show one or more graphical visualizations in one place that provide an overview of actionable business data. |
| Embedded Microsoft Power BI | Power BI adds embedded Power BI tiles and dashboards to your app. Power BI is a cloud-based service that provides business intelligence (BI) insight. |
Some examples of visualizations in a model-driven app:
Building model-driven apps
Model-driven apps are built using the App designer. It’s a simplified user interface that allows you to specify which tables the app is based on and which visual elements should be included. Let’s look at the App Designer for one of the available sample model-driven apps called “Fundraiser.”
This application includes two Dataverse tables: Donation and Fundraiser.
Once you define the tables for your app, you need to define the visual elements that are used to present the data to users. For each table, you need to specify the following information:
- Forms – Defines how users see and interact with individual records.
- Views – Defines how lists of rows are presented for each table. For example, you might create a view to display a list of all active fundraisers.
You can specify which specific forms or views to include for a table by selecting either the table form or view and choosing either Manage forms or Manage Views.
For example, the Account table in Dataverse includes all the columns defined for it. However, the data might not be relevant for each of your model driven applications. Let’s say that an organization created two model driven applications: Fundraiser and Innovation. In the fundraiser application, you would likely need details related to fundraising efforts such as an account’s tax exemption status. However, it’s likely that in the innovation application, you wouldn’t need that need that data. As a result, you would typically have two different account forms. One for the fundraising app with the tax exemption status details, and another for the innovation app without those fields.
It’s possible to include multiple forms and views per table. In the screenshot, we’re including multiple views to help manage donations. Only the selected forms are displayed. However, if you don’t select any view or forms, the system assumes that all items should be included in your app.
