add-sample-data

name	add-sample-data
description	This skill should be used when the user asks to "add sample data", "populate tables", "seed data", "add test records", "generate sample records", "insert demo data", "fill tables with data", "create test data", or wants to populate their Dataverse tables with sample records so they can test and demo their Power Pages site.
user-invocable	true
allowed-tools	Read, Write, Bash, Grep, Glob, AskUserQuestion, Task, TaskCreate, TaskUpdate, TaskList, mcp__plugin_power-pages_microsoft-learn__microsoft_docs_search, mcp__plugin_power-pages_microsoft-learn__microsoft_code_sample_search, mcp__plugin_power-pages_microsoft-learn__microsoft_docs_fetch
model	opus
hooks	{"Stop":[{"hooks":[{"type":"prompt","prompt":"If sample data was being added in this session (via /power-pages:add-sample-data), verify before allowing stop: 1) Tables were discovered (from .datamodel-manifest.json or OData API), 2) The user selected which tables to populate, 3) All records were inserted via OData API, 4) A verification summary was presented showing record counts per table. If incomplete, return { \"ok\": false, \"reason\": \"<specific issues>\" }. Otherwise return { \"ok\": true }.\n","timeout":30}]}]}

Add Sample Data

Populate Dataverse tables with sample records via OData API so users can test and demo their Power Pages sites.

Core Principles

• Respect insertion order: Always insert parent/referenced tables before child/referencing tables so lookup IDs are available when needed.
• Use TaskCreate/TaskUpdate: Track all progress throughout all phases -- create the todo list upfront with all phases before starting any work.
• Fail gracefully: On insertion failure, log the error and continue with remaining records -- never attempt automated rollback.

Initial request: $ARGUMENTS

---

Phase 1: Verify Prerequisites

Goal: Confirm PAC CLI auth, acquire an Azure CLI token, and verify API access

Actions:

1. Create todo list with all 6 phases (see Progress Tracking table)
2. Follow the prerequisite steps in ${CLAUDE_PLUGIN_ROOT}/references/dataverse-prerequisites.md to verify PAC CLI auth, acquire an Azure CLI token, and confirm API access. Store the environment URL as $envUrl.

Output: Authenticated session with valid token and confirmed API access

---

Phase 2: Discover Tables

Goal: Find the custom tables available in the user's Dataverse environment

Actions:

Path A: Read .datamodel-manifest.json (Preferred)

Check if .datamodel-manifest.json exists in the project root (written by the setup-datamodel skill). If it exists, read it -- it already contains table logical names, display names, and column info.

# Check if manifest exists
Test-Path ".datamodel-manifest.json"

See ${CLAUDE_PLUGIN_ROOT}/references/datamodel-manifest-schema.md for the full manifest schema.

Path B: Query OData API (Fallback)

If no manifest exists, discover custom tables via OData:

$tables = Invoke-RestMethod -Uri "$envUrl/api/data/v9.2/EntityDefinitions?`$select=LogicalName,DisplayName,EntitySetName&`$filter=IsCustomEntity eq true" -Headers $headers

For each discovered table, fetch its custom columns:

$columns = Invoke-RestMethod -Uri "$envUrl/api/data/v9.2/EntityDefinitions(LogicalName='<table>')/Attributes?`$select=LogicalName,DisplayName,AttributeType,RequiredLevel&`$filter=IsCustomAttribute eq true" -Headers $headers