version: "1.0.0" name: dataverse-web-resources description: > Use when creating, deploying, or managing Dataverse web resources for model-driven apps. Covers JavaScript form scripts (OnLoad, OnSave, OnChange events), HTML dashboard pages, CSS styling, image resources, navigation/side panes, ribbon/command bar customization, business process flow client API, and deployment via the Web API. Triggers on: "web resource", "javascript form", "form script", "html dashboard", "ribbon command", "onload event", "onchange event", "onsave event", "formContext", "Xrm.WebApi", "web resource deployment", "dashboard page", "form event handler", "side pane", "command bar", "ribbon", "modal dialog", "navigation", "Xrm.App", "Xrm.Navigation", "business process flow", "bpf", "stage change". license: MIT compatibility: "Dataverse Web API v9.2, Model-Driven Apps" metadata: author: custom version: "1.0.0" platform: "Microsoft Power Platform / Dataverse"

Dataverse Web Resources Skill

You are an expert in creating, deploying, and using Dataverse web resources within model-driven apps. Web resources are virtual files stored in Dataverse that can contain JavaScript, HTML, CSS, images, and other web content used to extend the application.

CRITICAL RULES

1. Always use a publisher prefix namespace for web resource names (e.g., cnt_/js/formscript.js).

The forward slash creates a virtual folder structure.

1. JavaScript must use the namespace pattern. Define all functions inside a namespace object

to avoid global scope pollution: ``javascript var MyApp = MyApp || {}; MyApp.FormScripts = { onLoad: function(executionContext) { ... } }; ``

1. Always pass `executionContext` to form event handlers. Enable "Pass execution context

as first parameter" when registering. Then: var formContext = executionContext.getFormContext();

1. Content must be base64-encoded when creating via the API. Use PowerShell's

[Convert]::ToBase64String() or equivalent.

1. Always publish after creating/updating web resources. They remain in draft until published.

1. 5MB size limit per web resource (configurable by org admin). Minify large JS/CSS.

1. Always consult `resources/ux-decision-guide.md` when choosing controls — before

selecting a control type, field format, navigation pattern, or page layout, check the decision guide for the recommended approach.

1. `Xrm` is NOT available in web resources loaded via MDA sitemap. Web resources loaded

as sitemap SubAreas run in an iframe where Xrm is not injected directly. Use this fallback chain: (1) Xrm.Utility.getGlobalContext(), (2) parent.Xrm.Utility.getGlobalContext(), (3) WhoAmI API call (GET /api/data/v9.2/WhoAmI) for user identity. Cache the result.

1. Sitemap web resource URL format: Use Url="/WebResources/{name}" (NOT $webresource:

prefix) on <SubArea> elements to embed HTML web resources as navigation items.

Quick Reference

Xrm Client API Quick Reference

Resource Files

• resources/types-reference.md -- All 12 web resource types with Type IDs and use cases
• resources/js-form-scripts.md -- JavaScript for form event handling, field validation, UI manipulation
• resources/html-dashboards.md -- HTML pages for dashboards, charts, and KPI displays
• resources/deployment.md -- Creating and deploying web resources via the API
• resources/navigation-side-panes.md -- Side panes, dialogs, navigation APIs (Xrm.App, Xrm.Navigation)
• resources/ribbon-command-bar.md -- Ribbon/command bar customization (modern + classic RibbonDiffXml)
• resources/ux-decision-guide.md -- Decision trees for control, layout, and navigation pattern selection
• resources/bpf-client-api.md -- Business Process Flow JavaScript API, events, stage navigation, common patterns