dataverse
Skill46 starsChanged 8 months agoMITView on GitHub
Dataverse Schema and Data Modeling. Use when: designing tables, columns, relationships, alternate keys, security roles, cascade behaviors, elastic tables, virtual tables, Dataverse search, query patterns (OData/FetchXML), naming conventions.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- JetBrains/skillstheir own version, first seen Nov 1, 2026
- stage2dev/power-platform-skillstheir own version, first seen Oct 2, 2026
- soulemike/microsoft-skillstheir own version, first seen Aug 18, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- JetBrains/skills★ 386same name
- stage2dev/power-platform-skills★ 3same name
- soulemike/microsoft-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- accessibility-uxSkill
- ai-builderSkill
- almSkill
- architectureSkill
- azure-openaiSkill
- business-process-flowsSkill
- canvas-appsSkill
- code-appsSkill
- code-reviewerSkill
- copilot-studioSkill
- custom-connectorsSkill
- dashboardsSkill
- data-migrationSkill
- dataverse-mcpSkill
- dataverse-web-apiSkill
- devops-engineerSkill
- env-strategySkill
- governanceSkill
- integration-patternsSkill
- licensingSkill
- m365-integrationSkill
- model-driven-appsSkill
- observabilitySkill
- pcfSkill
- perf-optimiseSkill
- platform-builderSkill
- pluginsSkill
- power-automateSkill
- power-biSkill
- power-pagesSkill
- power-platform-teamSkill
- project-managerSkill
- securitySkill
- solutions-architectSkill
- spec-driven-devSkill
- test-engineSkill
- testingSkill
- uat-coordinatorSkill
- web-resourcesSkill
The file
Files
Skill: Dataverse Schema & Data Modeling
When to Use
Trigger when designing tables, columns, relationships, security roles, views, or querying Dataverse via OData/FetchXML.
Table Type Selection
| Factor | Standard Table | Elastic Table | Virtual Table |
| Data volume | < 10M rows | 10M+ rows, high write throughput | External data (no copy) |
| Transactions | Full ACID (multi-record) | Per-record only | None |
| Security | Full row/column | Organization-owned only | Organization-owned only |
| BPF support | Yes | No | No |
| Charts/dashboards | Yes | No | No |
| Calculated/rollup | Yes | No | No |
| TTL auto-expiry | No | Yes | N/A |
| Offline support | Yes | No | No |
| Best for | Business data, CRUD apps | IoT, logs, telemetry, high-volume ingestion | Read-only external data (SQL, SharePoint, Fabric) |
⚠️ 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:
- Table Design — Table design principles, column type guide, auto-number columns, alternate keys
- Relationships — N:1, 1:N, N:N, manual intersect tables, cascade behaviors
- Query Patterns — OData queries, FetchXML, lookup handling in Code Apps, schema discovery via metadata API
- Naming Conventions — Publisher prefix, table/column/relationship naming standards
- Elastic & Virtual Tables — Elastic tables (Cosmos DB), virtual tables, Dataverse search, long-term retention
Anti-Patterns
- Text columns used as primary identifiers without alternate keys
- Cascade delete without documenting intended behavior
- Org-owned tables where row-level security is needed
- Rollup columns on tables with millions of rows
- Storing JSON blobs in text columns to avoid proper schema
- Duplicate choice definitions across tables (use global option sets)
- N:N relationship used when the intersect needs attributes
- Missing indexes on frequently-filtered lookup columns
- Over-permissive security roles ("just give them System Admin")
Related Skills
dataverse-web-api— CRUD operations and metadata management via APIsecurity— Security roles, column security, row-level accessplugins— Server-side logic operating on Dataverse schemacode-apps— Client-side Dataverse queries from Reactmodel-driven-apps— Forms and views built on Dataverse tables
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
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.

