add-dataverse · microsoft, code-apps — Claude Code skill for Power Apps tables
The add-dataverse Claude Code skill connects Dataverse tables to Power Apps code apps and generates TypeScript models and services. It also guides new table creation.
MIT ★ 1,167 updated 2026-10-29
/plugin marketplace add microsoft/power-platform-skills
/plugin install code-apps-preview@power-platform-skillsWhat add-dataverse does
For tables that already exist, the skill adds each one as a data source with pa app add data-source, reviews the generated files, then runs npm run build. The output includes TypeScript interfaces and services with CRUD methods. Tables with file or image columns also get related types and file operations.
For a new schema, the skill checks existing tables first and sorts candidates into reuse, extension, or creation. It presents a plan and waits for explicit approval before creating anything. API access requires an authenticated Azure CLI session and either the System Administrator or System Customizer security role. Without one of those roles, API-based table creation cannot proceed.
Before writing Dataverse code, the workflow calls for reviewing the Dataverse reference, which covers fields, relationships, and file columns. The skill fixes TypeScript build errors; deployment is outside its workflow.
What it helps with
- connect existing Dataverse tables to a Power Apps code app
- plan a table schema around its dependencies
- identify tables to reuse, extend, or create
- generate TypeScript models and CRUD services
- run a build and address TypeScript errors
Example prompts for the agent
- Connect the
accountandcontactDataverse tables to this Power Apps code app, then check the build. - Plan Dataverse tables for this data, inspect existing schemas, and show me the proposed creation order before making changes.
How to install add-dataverse
1Plugin marketplace
/plugin marketplace add microsoft/power-platform-skills/plugin install code-apps-preview@power-platform-skillsThis installs the whole code-apps-preview plugin with all its skills
2Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill add-dataverse -a claude-code3Manually: put the files in place
~/.claude/skills/add-dataverse/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/add-dataverse/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill add-dataverse -a codex2Manually: put the files in place
.agents/skills/add-dataverse/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill add-dataverse -a cursor2Manually: put the files in place
.cursor/skills/add-dataverse/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install microsoft/power-platform-skills plugins/code-apps/skills/add-dataverse2Manually: put the files in place
.github/skills/add-dataverse/SKILL.md1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill add-dataverse -a gemini-cli2Platform CLI
gemini skills install https://github.com/microsoft/power-platform-skills --path plugins/code-apps/skills/add-dataverseManually: put the files in place
.devin/skills/add-dataverse/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about add-dataverse
How do I install add-dataverse in Claude Code?
Add the marketplace with /plugin marketplace add microsoft/power-platform-skills, then install the plugin with /plugin install code-apps-preview@power-platform-skills.
What does add-dataverse do?
It connects Dataverse tables to a Power Apps code app and produces TypeScript models and services. It can also guide table design and creation.
What permissions are needed to create Dataverse tables?
The workflow requires an authenticated Azure CLI session and the System Administrator or System Customizer security role. It checks existing tables and asks for explicit approval before creating new ones.
Source text
SKILL.md · MIT
---
name: add-dataverse
description: Adds Dataverse tables to a Power Apps code app with generated TypeScript models and services. Can also create new Dataverse tables. Use when connecting to Dataverse, adding tables, creating schema, or querying Dataverse data.
user-invocable: true
allowed-tools: Read, Edit, Write, Grep, Glob, Bash, LSP, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, Skill, EnterPlanMode, ExitPlanMode
model: opus
---
**📋 Shared Instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** - Cross-cutting concerns.
**References:**
- [dataverse-reference.md](./references/dataverse-reference.md) - Picklist fields, virtual fields, lookups, file/image columns, form patterns (CRITICAL)
- [api-authentication-reference.md](./references/api-authentication-reference.md) - Dataverse API auth, token, publisher prefix
- [table-management-reference.md](./references/table-management-reference.md) - Query, create, extend tables and columns
- [data-architecture-reference.md](./references/data-architecture-reference.md) - Relationship types, dependency tiers
# Add Dataverse
Two paths: **existing tables** (skip to Step 5) or **new tables** (full workflow).
## Workflow
1. Plan → 2. Setup API Auth → 3. Review Existing Tables → 4. Create Tables → 5. Add Data Source → 6. Review Generated Files → 7. Build
---
### Step 1: Plan
Check memory bank for project context. Ask the user:
1. Which Dataverse table(s) do they need? (e.g., `account`, `contact`, `cr123_customentity`)
2. Do the tables **already exist** in their environment, or do they need to **create new** ones?
**If tables already exist:** Skip to Step 5.
**If creating new tables:**
- Ask about the data they need and design an appropriate schema
- Use standard Dataverse tables when appropriate (`contact` for people, `account` for organizations)
- Build a dependency graph -- see [data-architecture-reference.md](./references/data-architecture-reference.md) for tier classification
- Enter plan mode with `EnterPlanMode`, present ER model with tables, columns, relationships, and creation order
- Get approval with `ExitPlanMode`
### Step 2: Setup API Auth (if creating tables)
See [api-authentication-reference.md](./references/api-authentication-reference.md) for full details.
```powershell
az account show # Verify Azure CLI logged in
# Find your Dataverse environment URL:
# In make.powerapps.com → Settings → Developer resources → Web API endpoint
# It looks like: https://<org-name>.crm.dynamics.com/api/data/v9.2/
# Use the base URL: https://<org-name>.crm.dynamics.com
$api = Initialize-DataverseApi -EnvironmentUrl "https://<org>.crm.dynamics.com"
$headers = $api.Headers
$baseUrl = $api.BaseUrl
$publisherPrefix = $api.PublisherPrefix
```
Requires **System Administrator** or **System Customizer** security role.
### Step 3: Review Existing Tables (if creating tables)
**Always query existing tables first before creating:**
```powershell
$existingTables = Invoke-RestMethod -Uri "$baseUrl/EntityDefinitions?`$filter=IsCustomEntity eq true&`$select=SchemaName,LogicalName,DisplayName" -Headers $headers
```
See [table-management-reference.md](./references/table-management-reference.md) for `Find-SimilarTables`, `Compare-TableSchemas`, and `Build-TableNameMapping` functions.
Present findings to user with `AskUserQuestion`:
- Tables that can be **reused** (already exist with matching columns)
- Tables that need **extension** (exist but missing columns)
- Tables that must be **created** (no match found)
### Step 4: Create Tables (if creating tables)
Get explicit confirmation before creating. Create in dependency order:
- **Tier 0**: Reference tables (no dependencies)
- **Tier 1**: Primary entities (reference Tier 0)
- **Tier 2**: Dependent tables (reference Tier 1)
Use safe functions from [table-management-reference.md](./references/table-management-reference.md):
- `New-DataverseTableIfNotExists`
- `Add-DataverseColumnIfNotExists`
- `Add-DataverseLookupIfNotExists` (from [data-architecture-reference.md](./references/data-architecture-reference.md))
### Step 5: Add Data Source
For each table:
```bash
pa app add data-source --connector dataverse --table <table-logical-name>
```
Can add multiple tables by running the command for each one.
### Step 6: Review Generated Files
The command generates:
- `src/generated/models/{Table}Model.ts` -- TypeScript interfaces, plus `{Table}FileColumnName`, `{Table}ImageColumnName`, `{Table}UploadColumnName` union types if the table has file/image columns
- `src/generated/services/{Table}Service.ts` -- CRUD methods (create, get, getAll, update, delete) plus `upload`, `downloadFile`, `downloadImage`, `deleteFileOrImage` if file/image columns exist
Show the user a usage example:
```typescript
import { AccountsService } from "../generated/services/AccountsService";
const result = await AccountsService.getAll({
select: ["name", "accountnumber"],
filter: "statecode eq 0",
orderBy: ["name asc"],
top: 50
});
const accounts = result.data || [];
```
**Key rules:**
- Use generated services (e.g., `AccountsService.getAll()`), not fetch/axios
- Check `result.data` for actual data
- Don't edit generated files unless needed
- **Read [dataverse-reference.md](./references/dataverse-reference.md) before writing any Dataverse code** -- picklist fields, virtual fields, lookups, and file/image columns all have critical gotchas
### Step 7: Build
```bash
npm run build
```
Fix TypeScript errors before proceeding. Do NOT deploy yet.
### Update Memory Bank
Record which tables were added (or created), generated files, and any schema notes.
© Microsoft · MIT · microsoft/power-platform-skills
Similar skills
All skills for Data and databases →add-dataverse by other authors comes first.