Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Replace * in each affected Webapi/<table-logical-name>/fields site setting with the minimum comma-separated list of Dataverse column logical names your site needs. Alternatively, on Power Pages site version 9.8.8.x or later, use a public 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 treat this as a required migration, not a future cleanup.
What changed, and which sites are affected?
The deprecated wildcard is the * value in the Power Pages site setting Webapi/<table-name>/fields. It previously allowed all columns on that table through the Power Pages Web API. Microsoft states that newly created websites could no longer use it starting in August 2026, and requests to tables still using it fail beginning September 14, 2026. That enforcement date has passed.
This is a column allow-list change; it does not mean wildcard-like characters in Dataverse OData filters have all changed behavior. Microsoft’s separate OData filter guidance covers string matching with % and _ and notes that leading wildcard patterns are unsupported.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose how to define the allowed columns
| Option | How it works | Requirements and limits |
|---|---|---|
| Explicit fields list | Set Webapi/<table-logical-name>/fields to a comma-separated list of required column logical names. |
Manage the list in the site setting. Include only columns the application needs. |
| System view | Set Webapi/<table-logical-name>/UseFieldsFromView to True and create a public system view named Power Pages Web API Columns. |
Requires site version 9.8.8.x or later. Only displayed columns from the view’s primary table are included; related-table columns are not. View updates can take up to five minutes to become available. |
| Both | Configure the explicit list and the named view. | Eligible columns from both sources are combined, and duplicate column names are included once. |
The list is direct to inspect and adjust in site settings. A view lets you manage eligible columns through a Dataverse view, but it has the version and primary-table limitations shown above. Microsoft’s Power Pages Web API overview describes the configuration options.
#1 Best Overall
Inventory every column the site uses
Do not replace * with every column on the table. Build a per-table list from actual requests and the code that constructs and consumes them. Microsoft’s migration guidance, Power Pages Web API requests fail after wildcard column configuration is deprecated, recommends checking both client-side calls and response handling.
Find affected settings and API calls
- In the Portal Management app or Power Pages Management app, locate every setting named
Webapi/<table-name>/fieldswith value*. Check standard and custom Dataverse tables. - Search site code and components for calls such as
$.ajax(...),fetch(...),webapi.safeAjax(...),$pages.webAPI.retrieveRecord(...), and$pages.webAPI.retrieveMultipleRecords(...). - For each call, inspect the request and the code that reads its response. Record columns used in create or update payloads, response properties, and OData options including
$select,$filter,$orderby, and$expand.
Include query and relationship dependencies
Allow for columns used only to filter or sort, not just columns returned to the page. Review nested selections and relationship-related fields in $expand. For lookup columns, the Web API OData property form is _<column-logical-name>_value; make sure the needed lookup column is represented in the configuration using its Dataverse column logical name.
Apply the migration and test it safely
- For each affected table, replace
*with the minimum required comma-separated column logical names, configure the named view, or use both methods. Use the table’s logical name in the setting key—for example,account, not the entity set nameaccounts. - If using a view, confirm the site version is 9.8.8.x or later, the
UseFieldsFromViewsetting isTrue, and the public system view is named exactlyPower Pages Web API Columns. Display every required primary-table column, including those used only for filtering or sorting. - In a nonproduction environment, exercise each affected site feature and supported create, read, update, and delete operation. Test the relevant web roles and anonymous access if the site permits it.
- When a request fails, inspect it in browser developer tools. Check for missing columns as well as table permissions, column permissions, web roles, and whether
Webapi/<table-logical-name>/enabledis set toTrue. - Deploy the validated site settings and any system views to each environment, then repeat the relevant tests. Allow up to five minutes after publishing view changes for them to become available to the Web API.
If the wildcard requests still fail
- Confirm no affected
Webapi/<table-name>/fieldssetting still contains*, and check that each setting uses the table logical name. - Check that the allow list uses column logical names and covers payloads, response processing, query options, and expanded relationships.
- For view-based configuration, verify the site version, setting value, exact view name, and displayed primary-table columns. A related-table column will not be added by this view.
- Check permissions independently of the fields configuration: confirm Web API enablement, web roles, table permissions, and column permissions for the user and operation.
If an administrator cannot migrate immediately, Microsoft’s troubleshooting guidance says a one-time, short-term extension can be requested through Manage exemptions in the Power Platform admin center. It delays enforcement temporarily; it does not replace migration.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchMicrosoft’s Power Pages Release Version 9.8.8.x release notes, updated August 24, 2026, also identify Web API wildcard detection in Site Checker.
Quick Recap
Best Value
Rank #3
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.
