Study guide
4.1 Model-Driven App Design, Site Map Navigation & Modern App Designer
Microsoft Power Platform Functional Consultant PL-200
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Dataverse Tables, Relationships & Core Columns
1.1 Dataverse Table Types, Properties & Ownership 1.2 Table Relationships & Cascading Rules 1.3 Column Types, Formats, Primary Keys & Alternate Keys 1.4 Rollup, Calculated & Formula Columns with Power Fx
2 Chapter 2: Dataverse Data Management & Governance
2.1 Dataverse Search, Quick Find & Relevance Indexing 2.2 Auditing Configuration & Log Management 2.3 Duplicate Detection Rules & Settings 2.4 Bulk Record Operations, Data Import, Export & Templates
3 Chapter 3: Dataverse Security Model & Access Control
3.1 Business Units, Ownership Models & Modern BU Matrix 3.2 Security Roles, Privileges & Depth Levels 3.3 Teams Architecture: Owner, Access, and Microsoft Entra (AAD) Group Teams 3.4 Column-Level Security & Hierarchy Security Models
4 Chapter 4: Model-Driven App Fundamentals & Information Architecture
4.1 Model-Driven App Design, Site Map Navigation & Modern App Designer 4.2 Form Types: Main, Quick Create, Quick View & Card Forms 4.3 View Configuration, System Views, Personal Views & Filters
5 Chapter 5: Advanced Model-Driven App Components & Custom Pages
5.1 Custom Pages & Modern Commanding with Power Fx 5.2 Form Component Controls & Specialized UX Elements 5.3 Embedding Canvas Apps in Model-Driven Forms 5.4 Embedding Power BI Reports, Dashboards & Tiles
6 Chapter 6: Canvas Apps Structure, Formulas & Data Operations
6.1 Canvas App Architecture, Screens, Containers & Controls 6.2 Power Fx Formulas, Delegation & Data Source Limits 6.3 Variables (Context, Global), Collections & State Management 6.4 Triggering Power Automate Cloud Flows from Canvas Apps
7 Chapter 7: Power Pages Site Design, Navigation & Content
7.1 Power Pages Design Studio & Site Structure 7.2 Power Pages Templates, Styling & Responsive Layouts 7.3 Web Pages, Navigation Menus & Content Snippets
8 Chapter 8: Power Pages Data Integration, Forms & Web Roles
8.1 Power Pages Lists, Basic Forms & Advanced Forms 8.2 Table Permissions, Web Roles & Page Access Security 8.3 External Identity Providers & Authentication Configuration
9 Chapter 9: Power Automate Cloud Flow Fundamentals & Triggers
9.1 Cloud Flow Types: Automated, Instant, Scheduled & Desktop Overview 9.2 Dataverse Connector Triggers & Operational Filters 9.3 Standard Connectors, Custom Connectors & Connection References
10 Chapter 10: Cloud Flow Actions, Expressions & Logic Controls
10.1 Logic Controls: Conditions, Switches, Apply to Each & Do Until Loops 10.2 Variables, Data Operations & Dynamic Content Manipulation 10.3 Power Automate Expression Language (WDL / Functions) 10.4 Error Handling, Configure Run After & Scope Controls
11 Chapter 11: Business Process Flows & Guided Processes
11.1 Business Process Flow Architecture, Stages, Steps & Data Steps 11.2 Branching Rules & Multi-Entity Business Process Flows 11.3 BPF Action Steps, Workflows & Cloud Flow Execution 11.4 BPF Security Roles, Order & Process Lifecycle
12 Chapter 12: Classic Workflows, Business Rules & Modern Logic Extensibility
12.1 Classic Dataverse Workflows: Real-Time vs. Background (Async) 12.2 Business Rules: Scope & Actions 12.3 Low-Code Plug-ins in Dataverse: Automated vs. Instant 12.4 Troubleshooting Automations, Run History & Analytics
13 Chapter 13: Power Platform Environment Architecture & Security
13.1 Environment Types: Default, Sandbox, Production, Trial, Developer 13.2 Environment Governance, Groups, Routing & Capacity Management 13.3 Data Loss Prevention (DLP) Policies & Connector Classifications
14 Chapter 14: Application Lifecycle Management (ALM) & Solutions
14.1 Unmanaged vs. Managed Solutions & Solution Layering Mechanics 14.2 Solution Components, Dependencies, Publishers & Prefixes 14.3 Exporting, Importing, Upgrading & Patches 14.4 Solution Checker, App Checker & ALM Best Practices
15 Chapter 15: Enterprise Interoperability & Service Integration
15.1 Exchange / Server-Side Synchronization & Email Integration 15.2 SharePoint & OneDrive Document Management Integration 15.3 Microsoft Word & Excel Document Templates
16 Chapter 16: Copilot, AI Capabilities & Exam Strategy
16.1 Copilot Studio & Generative AI across Power Platform 16.2 AI Builder Prebuilt & Custom Models in Apps and Flows 16.3 PL-200 Exam Strategy, Time Management & Question Analysis
4.1 Model-Driven App Design, Site Map Navigation & Modern App Designer
Key Takeaways Explain This Topic AI
Model-driven apps are data-first, responsive business applications generated automatically from Dataverse data models, business logic, and security roles without requiring manual pixel layout.
The Modern App Designer provides a unified WYSIWYG authoring canvas with real-time live preview, multi-device responsiveness testing (desktop, tablet, mobile), and integrated page management.
The Site Map navigation architecture enforces a strict three-tier structural hierarchy: Area (top-level functional domain), Group (visual section heading), and Subarea (actionable clickable leaf node).
Site Map Subareas support four distinct content types: Table (Entity list/forms), Dashboard (classic or Power BI embedded), URL (external web page or intranet), and Web Resource (HTML/JavaScript component).
Model-driven app security operates on a dual-tier authorization model: users require Read privilege on the Model-driven App table (appmodule) via assigned Security Roles AND underlying table-level data privileges.
Last updated: August 2026
4.1 Model-Driven App Design, Site Map Navigation & Modern App Designer
In the Microsoft Power Platform ecosystem, Model-Driven Applications represent the enterprise standard for data-dense, process-centric business solutions. Unlike Canvas Apps—which start from a blank visual canvas and require makers to manually bind controls, write expressions, and design responsive layouts—Model-Driven Apps are data-first and component-driven . The user interface is dynamically rendered by the Unified Interface framework based entirely on the underlying Microsoft Dataverse schema, forms, views, business processes, and security architecture.
For a Power Platform Functional Consultant preparing for the PL-200 certification, mastering the Modern App Designer, understanding the mechanics of Site Map navigation hierarchies, configuring subarea content types, and implementing robust role-based app security are core competencies.
1. The Model-Driven Component Paradigm & Modern App Designer
Model-driven app development separates data architecture and business logic from visual presentation. When you build a model-driven app, you assemble modular components into a cohesive solution. The Unified Interface automatically handles responsive rendering across desktop displays, tablets, and mobile devices without custom CSS or viewport media queries. +-----------------------------------------------------------------------------------+
- | MODEL-DRIVEN APP COMPONENT-DRIVEN ARCHITECTURE |
- | |
- | +-----------------------------------------------------------------------------+ |
- | | 1. DATA LAYER (Dataverse Engine) | |
- | | - Standard & Custom Tables (Entities) | |
- | | - Columns (Attributes), Data Types, Choices & Formulas | |
- | | - Relationships (1:N, N:1, N:N) & Cascading Rules | |
- | +-----------------------------------------------------------------------------+ |
- | | 2. UI & NAVIGATION LAYER (Unified Interface) | |
- | | - Model-Driven Apps (`appmodule`) & App-Level Security Roles | |
- | | - Navigation Site Map: Area -> Group -> Subarea | |
- | | - Forms (Main, Quick Create, Quick View, Card) & Views (Public, System) | |
- | | - Dashboards, Power BI Embeds & Custom Pages | |
- | +-----------------------------------------------------------------------------+ |
- | | 3. LOGIC & AUTOMATION LAYER | |
- | | - Business Process Flows (BPFs) & Task Flows | |
- | | - Business Rules (Client-Side & Server-Side Validation) | |
- | | - Automated & Instant Power Automate Cloud Flows | |
- | | - Classic Workflows & Custom Dataverse Plugins | |
- | +-----------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------+
- Modern App Designer vs. Classic App Designer
Historically, model-driven apps were authored using the Classic Solution Explorer and Classic App Designer. Microsoft has superseded this with the Modern App Designer inside the Power Apps Maker Portal ( make.powerapps.com ).
Capability / Feature Modern App Designer ( make.powerapps.com ) Classic App Designer (Legacy)
Authoring Canvas Live interactive WYSIWYG preview with live data Static artifact matrix and component tile grid
Page Management Add Dataverse tables, custom pages, dashboards, URLs via unified left rail Separate XML Site Map designer and component checklist
Multi-Device Simulation One-click real-time preview for Desktop, Tablet, and Mobile viewports Requires launching published app in separate browser tabs
Custom Page Integration Native inline authoring of converging Canvas Custom Pages Not natively supported; required custom iframe/web resource
Navigation Editing Drag-and-drop Site Map reordering directly in left pane External visual Site Map editor requiring separate publish steps
App-Level Settings Modern panel for App Name, Description, Unique URL suffix, and Icon Classic properties dialog requiring hex color and 32x32 web resources
Note
The Modern App Designer introduces Custom Pages , which bridge the gap between Model-Driven and Canvas apps. Custom Pages bring the pixel-perfect flexibility and custom connectors of Canvas apps directly into model-driven navigation panes, dialogs, or full-page views.
2. Navigation Architecture: The Area -> Group -> Subarea Hierarchy
The backbone of every model-driven app is its Site Map . The site map defines the navigation pane displayed on the left side of the Unified Interface. Dataverse enforces a strict three-level hierarchical structure for site maps: +-----------------------------------------------------------------------------------+
- | SITE MAP HIERARCHICAL TOPOLOGY |
- | |
- | [AREA: Sales] (Top-Level Functional Domain Switcher) |
- | | |
- | +---> [GROUP: My Work] (Collapsible Visual Section Heading) |
- | | | |
- | | +---> [SUBAREA: Dashboards] (Content Type: Dashboard) |
- | | +---> [SUBAREA: Activities] (Content Type: Table -> Activity) |
- | | |
- | +---> [GROUP: Customers] (Collapsible Visual Section Heading) |
- | | | |
- | | +---> [SUBAREA: Accounts] (Content Type: Table -> Account) |
- | | +---> [SUBAREA: Contacts] (Content Type: Table -> Contact) |
- | |
- | [AREA: Settings] (Secondary Functional Domain Switcher) |
- | | |
- | +---> [GROUP: Configuration] |
- | +---> [SUBAREA: Product Catalog] (Content Type: Table -> Product) |
- | +---> [SUBAREA: Training Portal] (Content Type: URL -> External) |
- +-----------------------------------------------------------------------------------+
- The Three Hierarchical Levels
Area ( <Area> ):
The top-level functional domain container. Areas partition large enterprise applications into distinct operational zones (such as Sales , Service , Marketing , or Administration ).
Display Behavior: In the Unified Interface, when an app contains two or more Areas , Dataverse renders an Area Switcher dropdown at the bottom of the left navigation pane. If an app contains only one Area , the area switcher is automatically suppressed to conserve screen space.
Properties: ID, Title (localized display string), Icon, and Security Role / SKU privileges.
Group ( <Group> ):
A logical category header within an Area that organizes related subareas. For example, within the Sales Area, you might define Groups named My Work , Customers , and Collateral .
Display Behavior: Groups render as non-clickable bold section headings in the navigation rail. Users can expand or collapse groups to manage screen clutter.
Properties: ID, Title, and localized display names.
Subarea ( <SubArea> ):
The actionable, clickable leaf node within a Group. Clicking a Subarea navigates the user to a specific record grid, dashboard, external URL, or custom component in the primary application viewport.
Properties: ID, Content Type, Target Entity/Dashboard/URL/Resource, Icon, Title, Default Vector Icon, and Client availability flags.
3. Subarea Content Types & Configuration Properties
When configuring a Subarea in the Modern App Designer, you must select one of four fundamental Content Types : +-----------------------------------------------------------------------------------+
- | SUBAREA CONTENT TYPES MATRIX |
- | |
- | 1. TABLE (Entity) 2. DASHBOARD 3. URL 4. WEB RESOURCE |
- | +-----------------+ +-----------------+ +-----------------+ +-----------------+|
- | | Account | | Sales Hub Dash | | https://corp... | | custom_view.html||
- | | Contact | | Power BI Embed | | SharePoint Lib | | React Web Control||
- | | Opportunity | | Tier 1 Service | | Help Wiki Portal| | Silverlight/SVG ||
- | +-----------------+ +-----------------+ +-----------------+ +-----------------+|
- | Loads Entity Grid Loads Interactive Loads External Loads Solution-aware|
- | & Entity Forms Data Visualizations Webpage / Intranet Custom HTML/JS code|
- +-----------------------------------------------------------------------------------+
- In-Depth Content Type Comparison
Content Type Primary Usage Scenario Required Parameters Behavioral Characteristics
Table (Entity) Primary data management for standard or custom Dataverse tables Target Table Name (e.g., account , opportunity ) Automatically loads the entity's Default Public View grid. Automatically exposes entity forms, ribbon commands, and subgrids.
Dashboard Executive overviews, operational monitoring, and real-time KPI metrics Default Dashboard Name (Classic or Power BI Embedded) Displays interactive charts, multi-entity streams, or embedded Power BI reports. Allows users to switch dashboards via the dashboard selector.
URL Integrating corporate intranets, SharePoint document libraries, training portals, or external SaaS tools Absolute URL ( https://... ) or relative web address Loads web destinations directly inside the main app viewport or in a new browser tab. Can pass parameter context (org name, user ID).
Web Resource Bespoke solution-aware UI components, custom HTML forms, SVG visualizations, or JavaScript extensions Solution Web Resource Name (e.g., new_inventory_map.html ) Executes client-side web components packaged within Dataverse solutions. Supports REST API interaction with Dataverse.
Advanced Subarea Configuration Options
Client Availability: You can configure whether a subarea is accessible on Web (Browser) , Outlook (Dynamics 365 App for Outlook) , and Mobile (Power Apps Mobile Client) .
Check Privileges (Security Trimming): By default, Dataverse applies automatic security trimming. If a subarea points to a Table for which the logged-in user has zero Read permissions, Dataverse automatically hides that subarea from the navigation pane.
Explicit Parameter Passing: For URL and Web Resource subareas, you can enable "Pass record object-type code and unique identifier as parameters" to transmit runtime context.
4. App Access Security, Role Assignment & Sharing Mechanics
Deploying a model-driven application into an enterprise environment requires a clear understanding of the Two-Tier Security Model . Access to a model-driven app is governed by two separate authorization layers: +-----------------------------------------------------------------------------------+
- | TWO-TIER MODEL-DRIVEN APP SECURITY EVALUATION |
- | |
- | USER ATTEMPTS ACCESS: https://org.crm.dynamics.com/main.aspx?appid=abc-123 |
- | |
- | [TIER 1: APP MODULE ACCESS] ------------------------------------------------+ |
- | Does the user's Security Role grant access to this specific Model-Driven App?| |
- | | | |
- | +---> NO ===> [HTTP 403 / Access Denied: App Not Assigned] | |
- | | | |
- | +---> YES ===> Proceed to Tier 2 Evaluation | |
- | | |
- | [TIER 2: DATAVERSE DATA PRIVILEGES] ----------------------------------------+ |
- | Does the user hold Read/Write privileges for the tables in the Site Map? | |
- | | | |
- | +---> NO ===> Navigation Subareas trimmed / Data fields hidden | |
- | | | |
- | +---> YES ===> Full access to entity grids, forms, and command bars | |
- +-----------------------------------------------------------------------------------+
- Tier 1: App Module Privilege & Role Assignment
In Dataverse, every model-driven app is cataloged as a record in the App Module ( appmodule ) system table.
To open an app, a user must hold at least one Security Role that has been explicitly assigned to the app in the App Sharing panel or Power Platform Admin Center.
System Administrators and System Customizers have access to all model-driven apps by default.
If a user has valid table privileges across the database but is not assigned an app's security role, the app tile will not appear in their Office 365 app launcher or Power Apps portal, and direct URL access will fail with an authorization error.
Tier 2: Underlying Dataverse Table Privileges
App role assignment grants access only to the shell and navigation container of the application.
It does not grant automatic data permissions. If User A has access to the "Sales App" (Tier 1) but their assigned Security Role has Read = None on the Opportunity table, Dataverse security will either hide the Opportunity subarea entirely or display an "Insufficient Permissions" banner upon navigation.
URL-Based App Sharing & Distribution
Model-driven apps can be shared directly using their unique web address. The Unified Interface uses a deterministic URL structure: App URL = https:// ⟨ environment-name ⟩ .crm.dynamics.com/main.aspx?appid= ⟨ app-guid ⟩ \text{App URL} = \text{https://}\langle\text{environment-name}\rangle\text{.crm.dynamics.com/main.aspx?appid=}\langle\text{app-guid}\rangle App URL = https:// ⟨ environment-name ⟩ .crm.dynamics.com/main.aspx?appid= ⟨ app-guid ⟩
Unique App Name / URL Suffix: Makers can define a human-friendly URL suffix (e.g., https://contoso.crm.dynamics.com/apps/fieldservice ) in app properties to simplify bookmarking and corporate distribution.
Direct Deep Linking: Functional consultants can construct deep links directly to specific forms, entity records, or views by appending parameters such as &pagetype=entityrecord&etn=account&id=<record-guid> .