Starting this month, August 2026, Microsoft will deprecate the use of the wildcard value (*) in the webapi/<table-name>/fields site settings. This wildcard value which exposes all columns in a Dataverse table through the Power Pages Web API will no longer be allowed.
In August 2026, any newly created web site will no longer be able to use the wildcard value in this site settings. Following that, on September 14th, the support for the wildcard value (*) will be removed for all websites, which means that any websites must use an explicit list of allowed columns.
If any of the websites that you have developed are using the wildcard value in the webapi/<table>/<fields> site setting, you will need to modify this to use the specific columns that you need so that it remains accessible via the Power Pages Web API prior to the date mentioned. Not making this change will likely cause some potential disruptions in your application.
The reason for this is that the wildcard can unintentionally expose additional columns through the Web API that were not intended to be exposed. This change will improve security in your Power Pages application and prevent unnecessary access to columns that were not intended to be exposed.
You can read more about this deprecation notice here.
If you need to make this feature a little easier, you can use the Entity and Attribute Collection PCF controls from the PCF Metadata project that I created. This will allow you to select multiple fields and will created a comma separated list of fields as shown below. Note that the actual value of the field does not include the Display name or parenthesis, only the schema name.
This is a quick sample of how you can modify the Site Settings table to include additional columns and a little script so that you can use these PCF controls in it. I did not have time to fully implement it, but will do this and post it in a repo for anyone who might want to use these.
