microsoft/power-platform-skills / plugins/power-pages/skills/migrate-webapi-selectall
migrate-webapi-selectall
VerifiedReviews and migrates deprecated wildcard (*) values in Power Pages Web API fields site settings to least-privilege explicit Dataverse columns. Use whenever a user mentions Web API wildcard or select-all remediation, fields settings containing *, data-exposure review, wildcard deprecation readiness, or Web API failures after wildcard retirement. Applies to both non-SPA sites using HTML, CSS, JavaScript, Liquid, and downloaded YAML, and SPA sites using React, Vue, Angular, Astro, or TypeScript. The agent must inspect every source Web API call and consumer, report exact fixes for every wildcard, report every already-explicit configuration, apply approved edits, and verify no wildcard remains.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.1 KB |
| assets/migration-report-template.html | other | 17.4 KB |
| references/column-analysis.md | markdown | 4.7 KB |
| references/configuration-and-reporting.md | markdown | 6.0 KB |
| references/site-transfer.md | markdown | 3.6 KB |
| scripts/query-table-schema.js | script | 15.0 KB |
| scripts/render-migration-report.js | script | 2.2 KB |
references/column-analysis.md
View on GitHub# Column Analysis Rules
Use these rules to determine the smallest explicit field list that preserves
each Power Pages Web API operation. Read every call chain and consumer; static
search results are an inventory, not the final answer.
## Contents
- [Evidence priority](#evidence-priority)
- [Endpoint mapping](#endpoint-mapping)
- [Read operations](#read-operations)
- [Write operations](#write-operations)
- [File and image operations](#file-and-image-operations)
- [Dynamic code](#dynamic-code)
- [Configuration proposal](#configuration-proposal)
## Evidence priority
Prefer evidence in this order:
1. Request syntax: `$select`, `$expand`, property paths, FetchXML, `$filter`,
`$orderby`, and `$apply`.
2. Write payloads: POST, PATCH, PUT, deep inserts, and `@odata.bind`.
3. Response consumers: property access, destructuring, mappers, templates,
framework bindings, and TypeScript interfaces.
4. Shared builders: callers, defaults, conditional branches, and runtime
configuration.
5. Dataverse schema: canonical attributes, entity sets, lookups, and
navigation properties.
6. User-confirmed integration contracts when repository evidence is
incomplete.
Do not mark a proposal ready while a source wrapper, branch, or response
consumer remains unread. Never substitute compiled or generated code for
missing source.
## Endpoint mapping
Power Pages request paths use `EntitySetName`.
`Webapi/<table>/fields` settings use the table logical name. These names are
not reliably related by pluralization, so map them through the schema snapshot.
Classify search, summarization, cloud-flow, and server-logic routes under
`/_api/` as non-table endpoints only after confirming their public API shape.
Do not silently omit an unfamiliar endpoint.
## Read operations
For each table-returning GET:
- include root `$select` columns;
- include columns used by `$filter` and `$orderby`;
- include lookup properties as `_<LogicalName>_value` when the lookup is read,
filtered, or expanded;
- assign nested `$select`, filter, and order columns to the expanded table;
- include FetchXML attributes, conditions, ordering, grouping, and aggregate
inputs on their owning entity or link-entity;
- include `$apply` group, filter, and aggregate inputs, excluding output
aliases;
- add `$select` when a normal record GET omits it, deriving the projection from
every response consumer.
Maintain two separate results:
- the response projection contains only columns returned to consumers;
- the fields-setting allowlist contains projection, filter, order, aggregate,
lookup, property-route, and write requirements.
Do not widen an existing `$select` with a filter-only, order-only,
grouping-only, or write-only column.
`$top`, `$skip`, `$count`, paging cookies, aggregate aliases, formatted-value
annotations, and filter literals are not Dataverse columns.
## Write operations
For POST, PATCH, and PUT:
- include every payload property mapped to a Dataverse attribute;
- include the exact case-sensitive Navigation Property before `@odata.bind`;
- resolve that property through relationship metadata rather than guessing from
the attribute SchemaName;
- trace variables passed to `JSON.stringify`, HTTP clients, and custom
wrappers;
- inspect conditional properties and every object spread source;
- assign deep-insert object fields to their related target table.
For property PUT or DELETE routes, include the property named in the URL. A
record DELETE adds no field requirement by itself, but the table setting still
needs a nonempty, evidence-backed field list.
## File and image operations
Treat file and image endpoints as explicit-column operations:
- include the file or image column in the route;
- include file name, size, MIME type, or image metadata only when separately
read;
- never retain `*` as a compatibility workaround.
## Dynamic code
Trace dynamic entity sets, column arrays, URL fragments, query strings,
request bodies, and FetchXML through every caller and runtime branch.
When values come from external configuration, obtain the owning contract or
user confirmation. Do not infer fields from labels, singularization, naming
conventions, or likely primary keys.
## Configuration proposal
For each logical table and configuration scope, compute the sorted union of
proven field identifiers across all reads and writes. Use exact Dataverse
LogicalNames for ordinary columns, `_<LogicalName>_value` for lookup reads, and
the exact Navigation Property before `@odata.bind` for relationship writes.
Every proposed identifier needs:
- a relative source path and line, or a user-confirmed contract;
- the operation requiring it;
- its exact metadata-canonical name.
Do not add every metadata attribute, speculative identifiers, unrelated
server-side fields, or columns owned by expanded target tables.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |