# Add Dataverse

Use when the user wants to add Dataverse tables (existing or new) to a Power Apps...

- Repository: https://github.com/microsoft/power-platform-skills (1098 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add microsoft/power-platform-skills --skill add-dataverse -g -a claude-code -y`
Codex: `npx skills add microsoft/power-platform-skills --skill add-dataverse -g -a codex -y`
Cursor: `npx skills add microsoft/power-platform-skills --skill add-dataverse -g -a cursor -y`
Gemini CLI: `npx skills add microsoft/power-platform-skills --skill add-dataverse -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add microsoft/power-platform-skills`

## Description

Use when the user wants to add Dataverse tables (existing or new) to a Power Apps mobile app, extend an existing Dataverse table with new columns, or apply an approved data model plan.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

> **Plugin check**: Run `node "${PLUGIN_ROOT}/scripts/check-version.js"` - if it outputs a message, show it to the user before proceeding.

**📋 Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)**, read first.

# Add Dataverse

**App root:** before any project read or command, execute
[app-working-directory.md](${PLUGIN_ROOT}/shared/references/app-working-directory.md).
Use its resolved absolute `working_dir` for every shell call and file tool,
including referenced commands and delegated skills; never inherit a prior `cd`.

**Entry routing:** use the shared [App feature entry points](../../shared/shared-instructions.md#app-feature-entry-points)
preflight before the workflow below.

**Invocation scope:** follow [Data-source invocation scope](../../shared/shared-instructions.md#data-source-invocation-scope)
before the workflow below. Standalone calls use this skill's own data-delta
approval and verification; do not start a full-app plan or screen workflow.

An existing plan alone does not mean it includes or approves the new request;
never replay the old Data Model instead of resolving the requested delta.

**Removal branch:** after resolving invocation scope, `--remove` or an approved app-binding
removal executes
[data-source-removal.md](../../shared/references/data-source-removal.md), then
returns without entering Steps 1-9. Removing a plan row is not implemented by
re-running table creation or by deleting Dataverse metadata. For a mixed edit,
the owner adds/refreshes first and invokes removal separately after consumer edits.

**Refresh branch:** after resolving invocation scope, `--refresh` or an approved service-only
refresh executes [Refresh a retained source](../../shared/references/data-source-removal.md#refresh-a-retained-source)
and returns before Steps 1-9. Preserve the exact `--data-source-name` and approved
binding identity. Do not replay schema writes, publish, or run `add-data-source`.

Two paths:

The rest: https://github.com/microsoft/power-platform-skills/blob/HEAD/plugins/mobile-apps/skills/add-dataverse/SKILL.md