Difference between revisions of "Model-driven apps"
| (16 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
== Main Concepts == | == Main Concepts == | ||
| − | The main building blocks for model-driven apps are entities, forms, fields, views, dashboards, charts and sitemap. Model-driven apps always has | + | The main building blocks for model-driven apps are entities, forms, fields, views, dashboards, charts and sitemap. Model-driven apps always has Dataverse as back-end, i.e. stores its data in Dataverse. The data model is decided and created before the actual app is created. When creating an app all you need is a name and then you specify in the [[sitemap]] what menu items should be included (e.g. entities, [[web resources]] or URLs). |
| + | |||
| + | The command bar is another part of model-driven apps. You can create new or modify existing command buttons. Use JavaScript or [[Power Fx]] to define how the buttons should behave. For a long time Ribbon Workbench has been used to modify commands (before - the Ribbon). Nowadays you can also use the native designer to modify buttons. Here is an article explaining the difference: [https://develop1.net/public/post/2021/07/25/RibbonWorkbench-vs-PowerFx Ribbon Workbench vs. Power Fx]. Also see [[Model-driven commanding]] | ||
The Dynamics apps Dynamics Sales and Dynamics Customer Service are examples of model-driven apps. There is also the possibility to create custom model-driven apps, either containing entities from Dynamics, custom entities only or with a combination of custom entities and entities from Dynamics. | The Dynamics apps Dynamics Sales and Dynamics Customer Service are examples of model-driven apps. There is also the possibility to create custom model-driven apps, either containing entities from Dynamics, custom entities only or with a combination of custom entities and entities from Dynamics. | ||
| Line 21: | Line 23: | ||
== Community Content == | == Community Content == | ||
| + | === Cheatsheets === | ||
| + | * [https://danikahil.com/2022/02/power-apps-model-drive-apps-quick-create-quick-view-card-forms-cheatsheet.html Power Apps – Model Driven Apps – Quick Create, Quick View, Card Forms Cheatsheet] by Dani Kahil 2022-02-22 | ||
| + | |||
| + | === Videos === | ||
| + | ==== How-to ==== | ||
| + | How to create the app when you have built the data model (created tables in Dataverse) | ||
| + | * [https://youtu.be/NcsKUtUN3SE Building a model-driven app in Power Apps] by 8-year-old Kaelyn and her mom. 😍 | ||
| + | * [https://youtu.be/4Syn84tqKJU Make a Power Apps Model Driven App in 3 minutes] by 365.training (Julie Yack) | ||
| + | |||
| + | How to create Business Rules which will be used for the tables included in your Model-driven app | ||
| + | * [https://youtu.be/MdOwCbzDux8 Model Driven Apps Business Rules in 10 minutes] by 365.training (Derik Bormann) | ||
| + | |||
| + | ==== General videos ==== | ||
| + | * [https://youtu.be/YsOVsQeUImc Building Custom Business Applications with Model-Driven apps and Dataverse (CDS)] by Lisa Crosbie | ||
| + | * [https://youtu.be/3yN0-qBL8nA Building first Power App Model Driven Application tutorial] by Pragmatics Works (Brian Knight) | ||
| + | |||
| + | === Articles === | ||
* [https://readyxrm.blog/2020/06/05/you-likely-dont-need-dynamics-crm-you-need-a-power-app/ You likely don't need Dynamics CRM you need a Power App] article by Nick Doelman Design productive main forms in model-driven apps] | * [https://readyxrm.blog/2020/06/05/you-likely-dont-need-dynamics-crm-you-need-a-power-app/ You likely don't need Dynamics CRM you need a Power App] article by Nick Doelman Design productive main forms in model-driven apps] | ||
| + | |||
== See also == | == See also == | ||
| − | [[Canvas apps]] | + | * [[Canvas apps]] |
| − | [[Common Data Service]] | + | * [[Common Data Service]] |
| − | [[Virtual Entities]] | + | * [[Virtual Entities]] |
| − | [[Dynamics 365]] | + | * [[Model-driven commanding]] |
| + | * [[Microsoft Dynamics 365]] | ||
| + | * [[Icons]] | ||
| + | * [[In-app notifications]] | ||
| + | * [[Settings]] | ||
[[Category:Maker]] | [[Category:Maker]] | ||
Latest revision as of 13:08, 8 March 2022
Model-driven apps is one of the app types within Power Apps, the other two being canvas apps and portals.
History
Microsoft announced the preview of model-driven apps on the 21st of March 2018.
Much of the concept of model-driven apps comes from Microsoft Dynamics CRM. Model-driven apps has become the new UI for Dynamics, former CRM parts. This new UI has been designed to work on both on web, tables and phones. The same design tools are used for making customizations and the same forms and views etc. are used no matter if you run your application on web, tablet or phone. This UI has also gone under the name "unified interface" - a name which implies that it is one and the same interface for web, phone and tablet.
Main Concepts
The main building blocks for model-driven apps are entities, forms, fields, views, dashboards, charts and sitemap. Model-driven apps always has Dataverse as back-end, i.e. stores its data in Dataverse. The data model is decided and created before the actual app is created. When creating an app all you need is a name and then you specify in the sitemap what menu items should be included (e.g. entities, web resources or URLs).
The command bar is another part of model-driven apps. You can create new or modify existing command buttons. Use JavaScript or Power Fx to define how the buttons should behave. For a long time Ribbon Workbench has been used to modify commands (before - the Ribbon). Nowadays you can also use the native designer to modify buttons. Here is an article explaining the difference: Ribbon Workbench vs. Power Fx. Also see Model-driven commanding
The Dynamics apps Dynamics Sales and Dynamics Customer Service are examples of model-driven apps. There is also the possibility to create custom model-driven apps, either containing entities from Dynamics, custom entities only or with a combination of custom entities and entities from Dynamics.
Use Cases
Model-driven apps are typically used when there is a need for managing several things within one app. With Business Process Flows the user types in information and gets help with in what order, i.e. where in their business process, information should be added.
Microsoft Resources
Community Content
Cheatsheets
- Power Apps – Model Driven Apps – Quick Create, Quick View, Card Forms Cheatsheet by Dani Kahil 2022-02-22
Videos
How-to
How to create the app when you have built the data model (created tables in Dataverse)
- Building a model-driven app in Power Apps by 8-year-old Kaelyn and her mom. 😍
- Make a Power Apps Model Driven App in 3 minutes by 365.training (Julie Yack)
How to create Business Rules which will be used for the tables included in your Model-driven app
- Model Driven Apps Business Rules in 10 minutes by 365.training (Derik Bormann)
General videos
- Building Custom Business Applications with Model-Driven apps and Dataverse (CDS) by Lisa Crosbie
- Building first Power App Model Driven Application tutorial by Pragmatics Works (Brian Knight)
Articles
- You likely don't need Dynamics CRM you need a Power App article by Nick Doelman Design productive main forms in model-driven apps]