dataverse

Name: dataverse
Availability: InStock
Author: korchard333

Design Dataverse schemas with tables, columns, relationships, and security configurations.

46|6|Updated Mar 31, 2026

Search Tags:#governance #data-modeling #schema-design #odata #table-design #dataverse #fetchxml

Ready to run

npx skills add https://github.com/korchard333/claude-power-platform-community --skill dataverse-korchard333

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dataverse
Source: https://github.com/korchard333/claude-power-platform-community/tree/main/.claude/skills/dataverse
Command: npx skills add https://github.com/korchard333/claude-power-platform-community --skill dataverse-korchard333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing robust Dataverse schemas and data models, including tables, columns, relationships, alternate keys, and security configurations, to support scalable, governed deployments across apps and integrations.

Core Features & Use Cases

Guidance on when to use Standard, Elastic, and Virtual tables, naming conventions, and query patterns (OData/FetchXML) for reliable data access.
Patterns for relationships (N:1, 1:N, N:N), security modeling, and performance considerations across Dataverse.
Real-world scenarios for building business apps, data integrations, and analytics with Dataverse data.

Quick Start

Review the sub-files in this skill directory to begin applying Dataverse schema design.

Frequently Asked Questions about dataverse

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

FAQPage Schema

How do I design a Dataverse schema with standard, elastic, and virtual tables?▼

Design Dataverse schemas by structuring tables, columns, relationships, and alternate keys. Apply best practices for naming conventions and choose between standard, elastic, and virtual tables based on your specific data integration and scalability requirements.

What is the best way to model relationships and security in Dataverse?▼

Model relationships and security in Dataverse using specific patterns for N:1, 1:N, and N:N connections. Implement security configurations alongside these relationship structures to ensure governed data access across your business apps and analytics.

When should I use virtual tables instead of standard tables in Dataverse?▼

Use virtual tables in Dataverse when integrating external data sources without duplicating records, while standard tables store data directly within the platform. Choose elastic tables for high-volume data ingestion scenarios requiring flexible schema designs.

Does Dataverse schema design affect OData and FetchXML query patterns?▼

Yes, Dataverse schema design directly impacts OData and FetchXML query patterns. Applying proper naming conventions and structuring relationships correctly during table design ensures reliable and optimized data retrieval across apps and integrations.

How do I configure alternate keys in a Dataverse data model?▼

Configure alternate keys in a Dataverse data model to define unique identifiers for rows outside the primary GUID. This schema design step is essential for reliable data integration and supports accurate FetchXML and OData queries.

What are the naming conventions for Dataverse table and column design?▼

Naming conventions for Dataverse table and column design enforce consistent schema structures across standard, elastic, and virtual tables. Following these best practices ensures governed deployments and reliable query execution for business applications.