− | 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]. | | 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]. |