agentleFS
korchard333korchard333/claude-power-platform-community/.claude/skills/dataverse/SKILL.md

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

The file

Files
SKILL.md

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

FactorStandard TableElastic TableVirtual Table
Data volume< 10M rows10M+ rows, high write throughputExternal data (no copy)
TransactionsFull ACID (multi-record)Per-record onlyNone
SecurityFull row/columnOrganization-owned onlyOrganization-owned only
BPF supportYesNoNo
Charts/dashboardsYesNoNo
Calculated/rollupYesNoNo
TTL auto-expiryNoYesN/A
Offline supportYesNoNo
Best forBusiness data, CRUD appsIoT, logs, telemetry, high-volume ingestionRead-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 API
  • security — Security roles, column security, row-level access
  • plugins — Server-side logic operating on Dataverse schema
  • code-apps — Client-side Dataverse queries from React
  • model-driven-apps — Forms and views built on Dataverse tables

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.