$ loading_
Generate sample Dataverse records for testing and demoing a Power Pages site.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "add-sample-data" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/add-sample-data/SKILL.md 2. Save it as ~/.claude/skills/add-sample-data/SKILL.md 3. Reload skills and tell me it's ready
Generate demo data for the Dataverse tables used by my Power Pages site, including Contacts, Orders, and Support Tickets. Insert 20 records per table with realistic values and proper relationships.
A set of well-structured sample records is inserted into the specified Dataverse tables for realistic site demos.
Insert seed data into the Dataverse tables in my test environment, covering different statuses, date ranges, and required-field combinations so I can test Power Pages forms and list pages.
Seed records are created to cover multiple test scenarios and validate page display and interaction logic.
Add example business data to the Customers, Projects, and Invoices tables in Dataverse for a sales demo. Ensure realistic relationships between customers and projects, and between projects and invoices.
A batch of business-related sample data is inserted and ready for sales or product demonstrations.
Plugin check: Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"— if it outputs a message, show it to the user before proceeding.
Populate Dataverse tables with sample records via OData API so users can test and demo their Power Pages sites.
Initial request: $ARGUMENTS
Goal: Confirm PAC CLI auth, acquire an Azure CLI token, and verify API access
Actions:
${CLAUDE_PLUGIN_ROOT}/references/dataverse-prerequisites.md to verify PAC CLI auth, acquire an Azure CLI token, and confirm API access. Note the environment URL as <envUrl> for subsequent script calls.Output: Authenticated session with valid token and confirmed API access
Goal: Find the custom tables available in the user's Dataverse environment
Actions:
.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.
See ${CLAUDE_PLUGIN_ROOT}/references/datamodel-manifest-schema.md for the full manifest schema.
If no manifest exists, discover custom tables via OData:
node "${CLAUDE_PLUGIN_ROOT}/scripts/dataverse-request.js" <envUrl> GET "EntityDefinitions?\$select=LogicalName,DisplayName,EntitySetName&\$filter=IsCustomEntity eq true"
For each discovered table, fetch its custom columns:
node "${CLAUDE_PLUGIN_ROOT}/scripts/dataverse-request.js" <envUrl> GET "EntityDefinitions(LogicalName='<table>')/Attributes?\$select=LogicalName,DisplayName,AttributeType,RequiredLevel&\$filter=IsCustomAttribute eq true"
Show the user the list of discovered tables with their columns so they can choose which to populate.
Output: List of discovered tables with their columns presented to the user
Goal: Gather user preferences on which tables to populate and how many records to create
Actions:
Use AskUserQuestion to ask which tables they want to populate (use multiSelect: true). List all discovered tables as options.
Use AskUserQuestion to ask how many sample records per table:
| Option | Description |
|---|---|
| 5 records | Quick test -- just enough to verify the setup |
| 10 records | Light demo data for basic testing |
| 25 records | Fuller dataset for realistic demos |
| Custom | Let the user specify a number |
Analyze relationships between selected tables. Parent/referenced tables must be inserted first so their IDs are available for child/referencing table lookups.
Build the insertion order:
Output: Confirmed table selection, record count, and insertion order
Goal: Generate contextually appropriate sample records and get user approval before inserting
Actions:
…
Integrate Power Automate cloud flows into Power Pages with generated metadata and code.
Set up Power Platform Pipelines for automated Power Pages deployments.
Review and fix Power Pages security headers, CSP, CORS, cookies, and embedding settings.
Run an end-to-end Power Pages security review with a consolidated HTML report.
Test deployed Power Pages sites with browsing, crawling, and API verification.
Create and execute a reviewable ALM plan for Power Pages deployments.
Create Dataverse tables, columns, and relationships from a proposed site data model.
Add Dataverse tables to Power Apps code apps with generated TypeScript services.
Connect AI to Microsoft Dataverse for everyday record CRUD operations.
Integrate Power Pages Web API into frontend with permissions and deployment.
Generate realistic, foreign-key-consistent synthetic test data for databases.
Add and verify a data source or connector in Power Apps Studio.