agentleFS
korchard333korchard333/claude-power-platform-community/.claude/skills/model-driven-apps/SKILL.md

model-driven-apps

Skill46 starsChanged 8 months agoMITView on GitHub

Model-Driven Apps Development. Use when: building Model-Driven Apps, forms, views, business rules, site map, command bar customization, custom pages, embedded Canvas Apps, subgrids, role-based form switching, generative pages.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not setting a Quick Find view (renders lookup search unusable or slow)

    line 133

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Model-Driven Apps

When to Use

Trigger when building, configuring, reviewing, or troubleshooting Model-Driven Apps — including forms, views, business rules, app modules, site maps, command bar customizations, custom pages, and generative pages.


When to Use Model-Driven Apps vs Alternatives

ScenarioBest ChoiceWhy
Standard Dataverse CRUD + business processModel-Driven AppBuilt-in forms, views, business rules, BPF
Custom pixel-perfect UICode AppFull React/TypeScript control
Mobile field work, offline, cameraCanvas AppPower Apps mobile, offline support
Complex dashboards / analyticsPower BI embedded in MDABetter charting, slicers
High-volume data admin (bulk edit)Model-Driven AppGrid editing, bulk update, advanced find
Citizen developer / quick UICanvas AppNo TypeScript needed

Key MDA strengths: Forms, views, charts, dashboards with zero custom code. Business rules on client and server. Role-based form switching, audit trail, duplicate detection, merge records. Offline mobile via Dynamics 365 mobile app.


App Module (Site Map) Structure

App Module
├── Navigation Groups
│   ├── Group: "Operations" → Subareas (entities)
│   └── Group: "Configuration" → Settings, Users
├── Dashboards
└── Security Roles (who can access this app)

Create App Module via Web API

POST /api/data/v9.2/appmodules
Content-Type: application/json

{
  "name": "Contoso Projects",
  "uniquename": "contoso_ProjectsApp",
  "description": "Project management app",
  "clienttype": 4,
  "isdefault": false
}

⚠️ REQUIRED: Load Sub-Files Before Implementation

SKILL.md is a summary only — it is NOT sufficient for implementation.

The detailed content (complete payloads, XML templates, working examples, edge-case handling) lives in sub-files in the same directory as this SKILL.md. Before writing any code, you MUST use read_file on the sub-files relevant to your task:

  • Forms — form types, Quick View, role-based switching, lookup/choice columns, embedded Canvas Apps, form performance
  • Views — view types, Quick Find, subgrids, Power Apps grid control, deprecated Editable Grid, view performance
  • Sitemap — sitemap XML schema, Area/Group/SubArea structure, single Area layout (left-nav vs bottom tabs), Titles format, IntroducedVersion requirement, dashboard navigation
  • Business Rules — scope options (Entity/AllForms/SpecificForm), supported actions, when NOT to use
  • Command Bar — Command Designer (no-code), modern JavaScript commands, Power Fx commands, lookup parameter naming for form pre-population
  • Custom Pages — Custom Pages vs embedded Canvas Apps, creating, navigating to, passing parameters
  • Generative Pages (Genux) — React 17 + Fluent UI V9 single-file components, DataAPI, RuntimeTypes, PAC CLI workflow, localization, sample templates

Microsoft 365 Copilot in Model-Driven Apps (Preview)

Note: The previous "Copilot chat" feature in MDA is deprecated (January 2026) for non-Dynamics 365 environments. Use M365 Copilot instead.

M365 Copilot requires a Microsoft 365 Copilot license. Provides AI-assisted record summarization, data exploration. Works within the MDA shell for D365 and custom MDA apps.


Deprecated & Removed Controls

ControlStatusDateReplacement
Editable GridDeprecatedMarch 2026Power Apps grid control
Hierarchy controlRemovedOctober 2025None (removed entirely)
Classic lookDeprecatedApril 2026Modern look (now default)
Rich Text Editor (classic)DeprecatedApril 2025Modern RTE (default)
Copilot chat (non-D365)DeprecatedJanuary 2026M365 Copilot
Autocomplete controlDeprecated—Standard lookup
Input mask controlDeprecated—Business rules + validation
Multimedia playerDeprecated—Custom PCF / web resource

Naming Conventions

ObjectConventionExample
App module[Publisher] [Domain] AppContoso Projects App
Form[Entity] [Audience] FormProject Admin Form
View (system)[Audience] - [Scope]My - Active Projects
Business rule[Trigger]: [Action]High Priority: Require Due Date
Command[Verb] [Entity]Approve Order
Dashboard[Audience] [Domain] DashboardManager Project Dashboard

ALM for Model-Driven Apps

All MDA configuration lives in solutions:
  - App module (site map), Forms, views, charts, Business rules
  - Command bar customizations, Security role assignments

Export / unpack: pac solution export → pac solution unpack --processCanvasApps true
Forms and views unpack to readable XML — review diffs carefully
Business rules unpack to XAML — treat as opaque, don't edit manually

Anti-Patterns

  • Using Editable Grid in new development (deprecated March 2026 — use Power Apps grid control)
  • Using hierarchy control (removed October 2025)
  • Relying on Copilot chat feature in non-D365 environments (deprecated January 2026)
  • Building Model-Driven Apps outside of solutions ("My Apps")
  • Using JavaScript where a Business Rule suffices (harder to maintain)
  • Business rules with scope "Entity" for UI-only logic (wastes server cycles)
  • More than 7 tabs on a form (unusable cognitive load)
  • Subgrids loading all records without default views (performance)
  • Advanced Find views in production dashboards (personal views break sharing)
  • Mixing managed and unmanaged customizations in the same environment
  • Hardcoded GUIDs in JavaScript form scripts
  • Not setting a Quick Find view (renders lookup search unusable or slow)

Related Skills

  • web-resources — JavaScript form scripts and ribbon customizations
  • canvas-apps — Embedded Canvas Apps in Model-Driven forms
  • dataverse — Underlying table, form, and view design
  • security — Security roles that control form and field visibility

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.