migrate-webapi-selectall

Migrates Power Pages Web API wildcard field settings to explicit least-privilege Dataverse columns.

808|167|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/microsoft/power-platform-skills --skill migrate-webapi-selectall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-webapi-selectall
Source: https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-pages/skills/migrate-webapi-selectall
Command: npx skills add https://github.com/microsoft/power-platform-skills --skill migrate-webapi-selectall

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Power Pages sites configured with wildcard (*) values in Web API fields site settings expose every Dataverse column and break when the wildcard is deprecated. This Skill reviews every Web API call and configuration scope, then replaces each wildcard with the smallest explicit column set proven by actual site behavior.

Core Features & Use Cases

  • Complete inventory: Scans traditional sites (HTML, JavaScript, Liquid, YAML) and SPA sites (React, Vue, Angular, Astro, TypeScript) for every Web API call, wrapper, and configuration scope including deployment profiles.
  • Schema-backed column resolution: Queries Dataverse table metadata via a bundled script to map entity sets to logical names and validate every proposed column.
  • Evidence-based migration with approval gates: Proposes exact replacements, applies approved edits, verifies with a fresh discovery pass, renders an HTML report, and deploys only after explicit user confirmation.
  • Use Case: A Power Pages site fails after wildcard retirement; the Skill traces every /_api/ call, derives the required columns per table, updates Webapi/<table>/fields settings, and deploys the verified configuration.

Quick Start

Ask the agent to migrate the Web API wildcard field settings in your Power Pages project to explicit least-privilege columns, optionally providing the project path.

Frequently Asked Questions about migrate-webapi-selectall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Power Pages Web API wildcard fields settings?

Run the migration against your Power Pages project root; it inventories every Webapi/<table>/fields setting, traces all source Web API calls, and replaces each wildcard with the smallest explicit column set proven by actual usage. Approved edits are verified and can be deployed via PAC CLI.

How to fix Power Pages Web API failures after wildcard deprecation?

Wildcard (*) values in Web API fields settings are no longer supported, so each table needs an explicit comma-separated column list. The Skill derives required columns from request syntax, write payloads, and response consumers, then validates them against Dataverse schema.

Does the migration support React or other SPA Power Pages sites?

Yes, it supports SPA sites built with React, Vue, Angular, Astro, or TypeScript alongside traditional sites using HTML, JavaScript, and Liquid. It excludes compiled build output and analyzes only editable source files.

Can the migration run smoke tests against a deployed Power Pages site?

Only read-path smoke tests run, and only after explicit user approval. The Skill never issues POST, PATCH, PUT, or DELETE requests against a deployed site because testing writes would destroy real record data.

What happens if a Web API call exists only in compiled output?

The migration stops with a missing-source blocker rather than guessing columns from compiled, minified, or generated code. You must locate the editable source before the migration can proceed.