Quick Tip: It’s Time to Move to the Word Add-in Data Picker

A thread on the BC community forum this week is a good trigger to make a point I’ve been meaning to make for a while: if you are still building Word report layouts through the classic XML Mapping pane, it is time to switch to the newer Word add-in data picker instead.

What triggered it

A user reports that until about a month ago, inserting a field through the XML Mapping pane in a Word layout, worked as expected: insert a Plain Text content control, map it to the dataset field, and it populates correctly.
As of August 2026, newly inserted fields stop getting mapped. The content control shows the literal placeholder text instead of the value, for example “Due Date” instead of an actual date like 2026-08-26.
Existing, previously mapped fields are unaffected. Hovering over them still shows the correct #Nav: XML path, and they still populate correctly when the report runs.

What the community found

No confirmed answer yet, but two useful workarounds came out of the replies:

Since existing mapped fields keep working and only new insertions break, the problem looks like it sits in Word’s own XML mapping layer rather than in Business Central or the report dataset. Worth checking whether the affected machines share the same Word or Microsoft 365 update channel, and testing on a different Word build if you can.
The cleaner fix: skip the classic XML Mapping pane entirely and use the Word add-in data picker instead, available since Business Central 2025 wave 2 (BC27). It inserts mapped dataset fields directly through Add Data in the add-in, without touching the legacy XML Mapping pane, so it is not exposed to whatever is going wrong there.

Why I’d make the switch now, not just as a workaround

The XML Mapping pane has been the standard way to build Word report layouts for years, and a lot of partners still default to it out of habit. That is exactly the kind of setup where a regression like this one goes unnoticed for a while, since most people are only ever touching fields that were mapped long ago and still work fine.

The Word add-in data picker is not just a bugfix path around this specific issue. It is the direction Microsoft is actually building in:

Fields are inserted directly through Add Data, no Developer tab, no XML Mapping pane, no hunting for the right custom XML part in a dropdown.
You are working against an interface designed for this exact task, rather than reusing Word’s generic XML mapping tooling to do something it was never really built for.
New layout development done through the add-in is not exposed to this class of problem in the legacy mapping layer, whatever the exact root cause turns out to be.

If you build or maintain report layouts regularly, do not wait for the XML Mapping pane to break on you before switching. ==> Start defaulting to the Word add-in data picker for new layout work now, and treat this forum thread as a good reason to finally retire the old habit.