dataverse-create-schema

Create and update Dataverse schema components via Web API and PowerShell.

1|1|Updated Sep 25, 2025
One-click install
npx skills add https://github.com/spaarke-dev/spaarke --skill dataverse-create-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dataverse-create-schema
Source: https://github.com/spaarke-dev/spaarke/tree/main/.claude/skills/dataverse-create-schema
Command: npx skills add https://github.com/spaarke-dev/spaarke --skill dataverse-create-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables programmatic creation and updating of Dataverse schema components (entities, attributes, relationships, and option sets) using the Dataverse Web API and PowerShell, enabling repeatable deployments.

Core Features & Use Cases

  • Create global option sets, entities, attributes, and relationships through idempotent Web API calls.
  • Extend existing Dataverse schemas across environments with consistent metadata deployments.
  • Use cases include provisioning new data models, updating fields, and establishing relationships in automation pipelines.

Quick Start

Prerequisites: Azure CLI, PAC CLI, and a target environment.

  1. Authenticate to Azure and obtain a token for Dataverse: az login; az account show
  2. Acquire the Dataverse API base URL for your environment
  3. Run the provided PowerShell deployment patterns to create or update schema components

Frequently Asked Questions about dataverse-create-schema

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

FAQPage Schema
How do I automate Dataverse schema creation using the Web API?

Automate Dataverse schema creation by running PowerShell deployment patterns that make idempotent Web API calls to provision entities, attributes, relationships, and option sets. This enables repeatable metadata deployments across multiple environments.

What's the best way to deploy Dataverse entities and relationships across environments?

Deploying Dataverse entities and relationships across environments is best handled by executing idempotent Web API calls through PowerShell scripts. This approach ensures consistent metadata definitions and clear sequencing for schema deployment.

Do I need Azure CLI and PAC CLI to update Dataverse schema components?

Yes, you need Azure CLI and PAC CLI to update Dataverse schema components. You must authenticate to Azure, obtain a Dataverse access token, and acquire the API base URL for your target environment before running PowerShell patterns.

Can I create global option sets in Dataverse programmatically with PowerShell?

Yes, you can create global option sets in Dataverse programmatically with PowerShell. The deployment patterns apply idempotent Web API calls to define and update option sets alongside entities, attributes, and relationships.

Does making idempotent Web API calls work for updating existing Dataverse attributes?

Yes, idempotent Web API calls work for updating existing Dataverse attributes. The automation patterns support both creating and updating schema components, allowing you to extend current data models without duplicating metadata.