ArticlesDevelopment 7 min readDeutsche Fassung

The Power Pages Wildcard Exception for Rich Text Files Is Gone. Use This Field List

Power Pages no longer accepts the wildcard for msdyn_richtextfile either. Microsoft's tutorial now lists the explicit fields, including msdyn_fileblob.

Updated 6 November 2026: there is no exception any more.

This post was first written before the wildcard removal and has been revised to match. Since 14 September 2026, * is not supported in Webapi/<table-name>/fields on any website, including msdyn_richtextfile. Requests on a table that still uses it fail until the configuration is migrated. An admin can request a one-time, short-term extension, which delays enforcement but does not remove the requirement.

What to do: set Webapi/msdyn_richtextfile/fields to msdyn_richtextfileid,msdyn_name,msdyn_imageblob,msdyn_fileblob,msdyn_parententityname,msdyn_parententity_fieldname,msdyn_parentid,statecode,statuscode and test both an image and a file attachment.

Sources: Configure the rich text editor control on Power Pages, Step 3.2 and Power Pages Web API requests fail after wildcard column configuration is deprecated.

The general wildcard fix is straightforward: replace Webapi/<table>/fields = * with an explicit column list. That now applies to every table, including the one where Microsoft's own tutorial used to recommend the wildcard.

msdyn_richtextfile, the attachment table behind the rich text editor control, is where that fix most easily goes wrong. This post covers why the obvious field list is incomplete, what it quietly breaks, and the full list.

Microsoft's tutorial used to say: use the wildcard

Step 3.2 of "Configure the rich text editor control on Power Pages" lists the site settings required to save and access image and file attachments. It used to give * as the value. It now gives this:

Site setting name Value
Webapi/msdyn_richtextfile/enabled true
Webapi/msdyn_richtextfile/fields msdyn_richtextfileid,msdyn_name,msdyn_imageblob,msdyn_fileblob,msdyn_parententityname,msdyn_parententity_fieldname,msdyn_parentid,statecode,statuscode

The tutorial also warns that msdyn_fileblob is required for file attachments even though it is read only, and that an incomplete list might let images work while files fail. On most tables an explicit list is simple, because your own code decides which columns it reads and writes, and you can list exactly those. msdyn_richtextfile is different: the consumer is a closed source PCF control, and it asks for different columns depending on what you are doing with it. Uploading an image is not the same request as uploading a file, and reading is not the same request as writing.

Note: This started as a real remediation, applied to a live customer environment as part of the general wildcard cleanup, not a hypothetical. The field list below is what fixed it, verified against Dataverse metadata, not guessed from the symptom.

Two blob columns, two different jobs

msdyn_richtextfile holds attachments for the rich text editor control, and it does that through two separate blob columns:

msdyn_imageblob

Base64 image content, set directly in the create payload. This is what a pasted or dragged PNG, JPG, or GIF uses.

msdyn_fileblob

A file column, read only in the Dataverse metadata (IsValidForCreate: false, IsValidForUpdate: false). Uploaded and downloaded through its own PUT/GET .../$value operation, not the normal create body.

That second part is the trap. msdyn_fileblob never appears as a settable field in a create or update payload, so a field list built by reading what the control actually writes will not include it. It still has to be present in Webapi/msdyn_richtextfile/fields, because the file column operation itself is permitted or blocked based on whether the column is in that list, independent of whether the column is writable through the normal payload.

What an obvious field list breaks

The generic wildcard fix, applied without knowing the above, tends to produce a field list built from the visible use case, image attachments:

Webapi/msdyn_richtextfile/fields  →  msdyn_imageblob,msdyn_parentid

Image attachments, paste or drag and drop of PNG, JPG, GIF, keep working. Existing file attachments, PDF, XLSX, ZIP, stop being readable. New ones cannot be created either, and the two failures come from different code paths with the same error code:

Power Pages Web API error response, JSON body, code 90040101, the attribute msdyn_fileblob in table msdyn_richtextfile is not enabled for the Web API

That is the read path, on msdyn_fileblob. The create path fails the same way on a different column, msdyn_parententityname, which the shortened list also left out. Two missing fields, two error messages, both HTTP error code 90040101, both from the same site setting.

Warning: Image attachments continuing to work after the change is not confirmation that the fix is complete. It only tells you that the image path did not need the columns you removed. File attachments are a separate, silent regression until someone tries to open one.

The complete field list

This is the list from step 3.2 of Microsoft's tutorial: the writable columns on msdyn_richtextfile, per the Dataverse entity reference, plus the read only file column the control still needs listed:

msdyn_richtextfileid,msdyn_name,msdyn_imageblob,msdyn_fileblob,msdyn_parententityname,msdyn_parententity_fieldname,msdyn_parentid,statecode,statuscode

This list covers both attachment types and both operations, read and create. Applied against the case above, image and file attachments both read and both created correctly again. It is not a one off finding either: the same shortened list pattern showed up on a second, unrelated portal, with an added trap, that table existed as two separate site setting records with different GUIDs. Easy to miss if you are counting table names in the deprecation cleanup instead of counting site setting rows.

Note: System columns such as OwnerId are excluded here on purpose. The client never sets them itself, so they do not belong in a fields list scoped to what your code actually reads or writes.

If you want to enumerate it yourself

The list above is verified for the current rich text editor control, but "closed source PCF control" means Microsoft can change what it requests in a future release without telling you. Do not copy the list blind if you can check it live instead:

  1. Query EntityDefinitions(LogicalName='msdyn_richtextfile')/Attributes against the Dataverse Web API and read the writable versus read only columns directly from the metadata, rather than from a blog post.
  2. Test both attachment paths for real: an image attachment and a file attachment, each read and newly created. Four checks, not two, because read and create fail independently.
  3. Check for duplicate site setting records on the exact same table name before you conclude the setting is fixed everywhere.
  4. If a request still fails, use the browser developer tools to find the missing column, add only that column, and test again. Do not fall back to *: it is no longer a supported value.

The general rule now has no exception. What makes this table harder is that it has a single, closed source consumer with variable field needs across scenarios, so a list that looks complete can still be wrong. That is why the four checks matter more here than on a table your own code calls.

Why my maintenance clients already knew

The case behind this post came from exactly this kind of remediation work: a table fixed once, incompletely, then fixed properly once the real field usage was checked against the metadata instead of assumed. That is the difference a systematic review makes, and it is part of what Power Pages Care covers every month, not just when something is visibly broken.

I look after your portal so you do not have to. This is not a support contract with a bucket of hours. Four things happen every month, whether or not anything is going on.

01 Security and configuration review

Table permissions, web roles, site settings and identity configuration checked systematically.

02 Microsoft release check with a clear verdict

I read the release notes and the deprecation notices, you get the verdict: what affects your portal, what needs action, what you can ignore.

03 Written monthly report

Status, findings, recommendations, open items, in a form that also works for audit and compliance.

04 Smaller adjustments included

A bug fix, a permission adjustment, a form change. Anything bigger is agreed upfront.

Care is 1,290 EUR net per month, with a 48 hour response time on business days and adjustments up to two hours a month. Care Plus is 2,490 EUR net and adds a quarterly deep dive covering one audit area at a time, a 24 hour response time, same day for security incidents, and adjustments up to five hours. Minimum term three months, monthly after that.

You always know who to call. Onepager and terms: Care (page in German). Questions go straight to tino@amingi.net.

Related Articles

Sources

Tino RabeDynamics 365 CRM & Power Platform Consultant · Power Pages SpecialistFormer Microsoft MVP for Power Pages

This post was written with AI assistance. The idea, the concept and the experience come from my project work, and every technical claim is verified by me, much of it reproduced in a live portal.