dataverse-web-resources

Create, deploy, and publish Dataverse web resources for model-driven apps.

56|16|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/DanielKerridge/claude-code-power-platform-skills --skill dataverse-web-resources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dataverse-web-resources
Source: https://github.com/DanielKerridge/claude-code-power-platform-skills/tree/main/dataverse-web-resources
Command: npx skills add https://github.com/DanielKerridge/claude-code-power-platform-skills --skill dataverse-web-resources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dataverse web resources are critical for extending model-driven apps, yet teams struggle with consistent creation, deployment, and publishing across environments. This skill consolidates best practices for creating, packaging, and versioning web resources (JS, HTML, CSS, images) and ensures consistent usage across forms, sitemaps, and dashboards.

Core Features & Use Cases

  • Standardizes creation and naming of web resources (publisher-prefixed paths like cnt_/js/*.js).
  • Provides deployment and publishing guidance via Dataverse Web API, including content encoding and versioning.
  • Shows patterns for integrating web resources into forms, dashboards, side panes, and sitemap navigations.
  • Use Case: reuse web resources across multiple forms and sitemaps to maintain a consistent UI and behavior.

Quick Start

Upload a new JavaScript web resource at cnt_/js/dashboard.js, publish it, and reference it in a form or sitemap to extend the app.

Frequently Asked Questions about dataverse-web-resources

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy Dataverse web resources for model-driven apps?

Deploy Dataverse web resources by uploading content via the Dataverse Web API using base64 encoding, requiring publisher prefixes in resource names, and publishing after create or update to apply changes.

What is the correct naming convention for Dataverse web resources?

Dataverse web resources require publisher-prefixed paths, such as cnt_/js/*.js, to standardize creation and maintain consistent usage across forms, sitemaps, and dashboards.

Why are my Dataverse web resource changes not showing up in model-driven apps?

Dataverse web resource changes require publishing after create or update to apply changes, ensuring consistent UI and behavior across environments in model-driven apps.

Can I reuse JavaScript web resources across multiple forms and sitemaps?

You can reuse web resources across multiple forms and sitemaps to maintain a consistent UI and behavior, applying JavaScript form scripts, HTML dashboards, CSS styles, and images across Dataverse model-driven apps.

Does deploying web resources via Dataverse Web API require base64 encoding?

Deploying web resources via the Dataverse Web API requires base64 encoding for content uploads, enabling consistent deployment and versioning of JavaScript, HTML, CSS, and image files.

What types of web resources can I manage for Dataverse model-driven apps?

You can manage JavaScript form scripts, HTML dashboards, CSS styles, and images as Dataverse web resources to extend model-driven apps and integrate them into forms, dashboards, and sitemap navigations.