Model-driven apps - Revision history

CarinaMClaesson at 13:08, 8 March 2022

2022-03-08T13:08:35Z

CarinaMClaesson: /* Community Content */

2022-03-08T13:08:00Z

Community Content

CarinaMClaesson at 11:29, 2 December 2021

2021-12-02T11:29:36Z

CarinaMClaesson at 19:47, 1 December 2021

2021-12-01T19:47:51Z

CarinaMClaesson at 13:32, 1 December 2021

2021-12-01T13:32:42Z

CarinaMClaesson at 13:32, 1 December 2021

2021-12-01T13:32:09Z

CarinaMClaesson at 13:31, 1 December 2021

2021-12-01T13:31:17Z

CarinaMClaesson at 10:40, 30 November 2021

2021-11-30T10:40:00Z

CarinaMClaesson at 08:02, 3 August 2021

2021-08-03T08:02:14Z

CarinaMClaesson at 07:14, 3 August 2021

2021-08-03T07:14:29Z

@@ Line 24: / Line 24: @@
 == Community Content ==
 === Cheatsheets ===
-* [https://danikahil.com/2022/02/power-apps-model-drive-apps-quick-create-quick-view-card-forms-cheatsheet.html Power Apps – Model Drive Apps – Quick Create, Quick View, Card Forms Cheatsheet] by Dani Kahil 2022-02-22
+* [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 ===

@@ Line 23: / Line 23: @@
 == Community Content ==
 === Videos ===
 ==== How-to ====
 How to create the app when you have built the data model (created tables in Dataverse)
@@ Line 39: / Line 41: @@
 === 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]
 == See also ==
 * [[Canvas apps]]

@@ Line 47: / Line 47: @@
 * [[Icons]]
 * [[In-app notifications]]
 [[Category:Maker]]

@@ Line 46: / Line 46: @@
 * [[Microsoft Dynamics 365]]
 * [[Icons]]
 [[Category:Maker]]

@@ Line 40: / Line 40: @@
 * [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 ==
-[[Canvas apps]]
+* [[Canvas apps]]
-[[Common Data Service]]
+* [[Common Data Service]]
-[[Virtual Entities]]
+* [[Virtual Entities]]
-[[Model-driven commanding]]
+* [[Model-driven commanding]]
-[[Dynamics 365]]
+* [[Microsoft Dynamics 365]]
-[[Icons]]
+* [[Icons]]
 [[Category:Maker]]

@@ Line 10: / Line 10: @@
 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].
+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.

@@ Line 8: / Line 8: @@
 == Main Concepts ==
-The main building blocks for model-driven apps are entities, forms, fields, views, dashboards, charts and sitemap. Model-driven apps always has Common Data Service as back-end, i.e. stores its data in the Common Data Service. 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 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].

← Older revision		Revision as of 07:14, 3 August 2021
Line 9:		Line 9:

	The main building blocks for model-driven apps are entities, forms, fields, views, dashboards, charts and sitemap. Model-driven apps always has Common Data Service as back-end, i.e. stores its data in the Common Data Service. 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 main building blocks for model-driven apps are entities, forms, fields, views, dashboards, charts and sitemap. Model-driven apps always has Common Data Service as back-end, i.e. stores its data in the Common Data Service. 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].

	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.