To fix Power Pages Web API requests that fail after the wildcard deprecation, replace each Webapi/<table-logical-name>/fields setting set to * with an explicit, minimal list of the Dataverse column logical names the site needs. Alternatively, use a Dataverse system view named Power Pages Web API Columns and set Webapi/<table-logical-name>/UseFieldsFromView to True. Microsoft says requests to tables still configured with * began failing on September 14, 2026, so a remaining wildcard is a migration issue, not a supported configuration.
What the wildcard change affects
The deprecated value is * in the Power Pages site setting Webapi/<table-name>/fields, which previously allowed all columns for a table through the portals Web API. Microsoft says newly created sites could not use this configuration beginning in August 2026, and requests to any table still configured with it began failing on September 14, 2026. See Microsoft’s Power Pages wildcard migration guidance.
As an Amazon Associate I earn from qualifying purchases.
This change is about the Web API column allow list. It does not change the separate wildcard-like characters used in Dataverse OData string filters; Microsoft documents those filter semantics separately in its OData filter guidance.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose an explicit field list, a system view, or both
| Option | How it works | Requirements and limits |
|---|---|---|
| Explicit fields list | Set Webapi/<table-logical-name>/fields to a comma-separated list of needed column logical names. |
Maintain the list in the site settings. Use the table logical name, such as account, not its entity set name, such as accounts. |
| System view | Set Webapi/<table-logical-name>/UseFieldsFromView to True and create a public system view named Power Pages Web API Columns. |
Requires Power Pages site version 9.8.8.x or later. Only displayed columns from the primary table are included; related-table columns are not. View changes can take up to five minutes to become available. |
| Both | Configure the explicit fields list and the system view. | Eligible columns from both sources are combined, with duplicate column names included once. |
Microsoft describes the settings and view behavior in its Power Pages portals Web API overview. Use an explicit list when you want the allowed columns visible directly in site settings; use the view when managing the displayed columns in Dataverse is a better fit. The view is not a way to include related-table columns automatically.
#1 Best Overall
Inventory every column the site uses
Do not replace * with every column on the table. Build the smallest list that supports the site’s actual Web API requests and the code that handles their results.
- In the Portal Management app or Power Pages Management app, find every site setting named
Webapi/<table-name>/fieldswhose value is*. Check standard and custom Dataverse tables. - Search client-side code and components for Web API calls, including
$.ajax(...),fetch(...),webapi.safeAjax(...),$pages.webAPI.retrieveRecord(...), and$pages.webAPI.retrieveMultipleRecords(...). - For each affected table, review both request construction and response-processing code. Record columns in create and update payloads, properties read from responses, and columns referenced in
$select,$filter,$orderby, and$expand, including nested selections and relationship-related fields. - Use column logical names in the explicit list. For lookup columns, the Web API OData property form is
_<column-logical-name>_value. If using the system view, make sure every needed primary-table column—including columns used only for filtering or sorting—is displayed.
Microsoft’s migration guidance recommends checking requests and the code that consumes them, rather than treating the response’s visible fields as the whole inventory.
Apply and validate the migration
- For each affected table, remove the wildcard value and configure the explicit comma-separated column list, the named system view with
UseFieldsFromView=True, or both. - In a nonproduction environment, exercise each affected feature and supported create, read, update, and delete operation. Test relevant web roles and anonymous access where applicable.
- Inspect failed requests in browser developer tools. A missing-column error can point to a field omitted from the allow list or view; also verify that the user’s permissions allow the operation.
- Deploy the validated site settings and any system views to each environment, then repeat the tests there. After publishing view changes, allow up to five minutes for them to become available to the Web API.
The allow list is not a substitute for authorization. Confirm that Webapi/<table-logical-name>/enabled is True and that the user’s web role, table permissions, and column permissions permit the operation. Microsoft’s Web API overview describes the configuration context.
What to do if migration cannot happen immediately
Microsoft’s troubleshooting guidance says an administrator who cannot migrate immediately can request a one-time, short-term extension through Manage exemptions in the Power Platform admin center. This only delays enforcement; it does not make the wildcard a valid long-term setting or replace migration. Treat it as a temporary contingency while you inventory, configure, and test the required columns.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
