Microsoft Dynamics 365 Customer Experience Analyst : Configure model-driven apps

Model-driven apps in Microsoft Power Apps are data-centric applications built on top of Microsoft Dataverse that provide a powerful way to rapidly design and deliver business solutions. Unlike canvas apps, where the focus is on pixel-perfect design, model-driven apps are defined by the underlying data model, relationships, and business processes. They automatically generate responsive, accessible user interfaces that adapt across devices, reducing development effort while maintaining consistency. With features like forms, views, dashboards, business rules, and workflows, model-driven apps are ideal for complex, enterprise-grade scenarios such as customer service, sales, and operations, ensuring users can interact with data in a structured and efficient way. 





 Configuring a Model-Driven App in Power Apps

Model-driven apps are driven by your data model in Dataverse, not by custom UI design like canvas apps. You configure them by defining tables, relationships, views, forms, and business logic.

1. Prerequisites
  •  A Power Apps or Dynamics 365 license with access to Dataverse.
  •  Permissions to create apps and customize tables.
  •  An environment with Dataverse enabled.
2. Create a New Model-Driven App

1. Sign in to Power Apps Maker Portal → [https://make.powerapps.com](https://make.powerapps.com).
2. Select Apps → + New app → Model-driven app.
3. Give the app a Name, Unique name, and Description.
4. Choose a Solution (recommended: create apps inside a solution for ALM).
5. Select Modern app designer (new experience) or Classic app designer.

3. Configure Navigation (Sitemap)

The sitemap defines the navigation structure of your app.
  •  Add Areas (like Sales, Service).
  •  Add Groups (logical categories).
  •  Add Subareas (links to specific tables, dashboards, or web resources).
Example:

 Area: Customer Service

   Group: Cases Management

     Subarea: Cases Table

4. Choose Tables and Components

Select which Dataverse tables should be part of the app (e.g., Accounts, Contacts, Opportunities).
 For each table, you can configure:
  • Forms → Layouts for data entry (e.g., Main form, Quick Create form).
  • Views → How data is displayed in grids (e.g., Active Cases, My Contacts).
  • Charts & Dashboards → Visualize KPIs and data insights.


5. Define Business Logic

Model-driven apps are powerful because they enforce business rules and automation. You can configure:
  • Business Rules → Apply logic (e.g., make a field mandatory if another field is filled).
  • Workflows / Power Automate → Automate tasks (e.g., send email when a case is created).
  • Business Process Flows (BPFs) → Guide users through multi-stage processes (e.g., Lead to Opportunity).
  • Security Roles → Control who can access tables, fields, and records.


6. Apply Security and Permissions
  •  Assign Security Roles to the app so only authorized users can access it.
  •  Configure table-level security (Create, Read, Write, Delete, Append, Share).
  •  Optionally apply field-level security for sensitive data.
7. Test and Publish

1. Save and Publish the app.
2. Open it in a browser → validate navigation, forms, and data access.
3. Test with users under different roles.
4. Deploy to end users through Power Apps, Dynamics 365, or by sharing via URL.

 8. Best Practices
  •  Always build model-driven apps inside a Solution for better ALM and portability.
  •  Keep sitemap navigation simple — don’t overload with too many tables.
  •  Use different forms for different roles (e.g., Salesperson vs. Manager).
  •  Regularly review views and dashboards to ensure they match business needs.
  •  Leverage Dataverse Search and Advanced Find for better usability.


Example Scenario:

If you’re building a Customer Service App:
  •  Tables: Cases, Contacts, Accounts, Knowledge Articles.
  •  Sitemap: Cases → Active Cases, Resolved Cases.
  •  Forms: Case Main Form with fields like Case Title, Customer, Priority.
  •  BPF: Case Resolution Process.
  •  Dashboard: Open Cases by Priority.

Summary:

Configuring a model-driven app in Power Apps involves building data-centric business applications based on Microsoft Dataverse. The process starts with creating the app in the Power Apps Maker portal and defining the sitemap navigation (areas, groups, subareas). You then select the tables, forms, views, charts, and dashboards that the app will use. To enforce business logic, you can add business rules, workflows, and business process flows, while security roles control access to data and app components. Finally, the app is tested, published, and shared with users. Model-driven apps automatically generate responsive interfaces, making them ideal for enterprise scenarios like sales, service, and operations where structured data and guided processes are critical.

Comments

Post a Comment

Popular posts from this blog

Effective Strategies for Debugging Plugins in Dynamics CRM

Image
In a recent interview, I was asked about debugging plugins in Dynamics CRM. The interviewer specifically wanted to know my approach to plugin debugging. In response, I mentioned using the Plugin Registration Tool profiler. However, I later realized there are multiple methods to debug plugins in Dynamics CRM/Dataverse, each essential for efficient troubleshooting. Debugging plays a crucial role in development, and having a solid understanding of various debugging approaches can help streamline issue resolution in Dynamics 365. Here, I'll explore different techniques for debugging plugin code. There are below options to use in the plugin in Dynamics CRM/Dataverse ITracingService : In Dynamics CRM plugin development, ITracingService is a service provided within the plugin's execution context that logs information for tracing and debugging. It allows developers to capture real-time. Plugin Profiler : A plugin profiler in Dynamics CRM (or Dataverse) is a debugging tool in the Plugi...
Read more

Exploring the Differences: Managed vs. Unmanaged Solutions in Dynamics CRM/Dataverse

Image
In Dynamics CRM/Dataverse, solutions are central to Application Lifecycle Management (ALM) , providing a structured way to manage, package, and distribute customizations across environments. Microsoft uses solutions to transfer apps and customizations by exporting them from one Dataverse environment and importing them into another.  Each solution is authored and maintained by a publisher and includes components like Power Apps (canvas and model-driven), flows, entities, forms, connectors, web resources, and configurations—excluding business data. Solutions streamline ALM practices within Microsoft Power Platform. In Dynamics CRM/Dataverse, there are two types of solutions: Managed and Unmanaged . When planning an implementation, it’s important to understand the advantages and disadvantages of each to make an informed decision. Let’s explore both types to determine the best approach for development and deployment. In Dynamics 365 CRM, a managed solution is a fully packaged solution ...
Read more

Connecting the Dots: FetchXML and Web API Integration in Dataverse

Image
 In Dataverse, FetchXML and the Web API are two powerful mechanisms for retrieving data and interacting with entities. Here's a brief overview of each and how they can be integrated: 1.    FetchXML :      -   Definition:   FetchXML is a proprietary query language used in Microsoft Dynamics 365 and Dataverse for querying data from entities.    -   Usage:   FetchXML queries can be used to retrieve data based on complex criteria, perform aggregations, and filter records.    -   Features:   FetchXML supports various query expressions, including conditions, sorting, grouping, and aggregation functions.    -   Integration:   FetchXML queries can be executed programmatically using client-side scripting, server-side code, or through tools like the Dynamics 365 Web API. 2.    Web API :      -   Definition:  ...
Read more