Quick Tip: It’s Time to Move to the Word Add-in Data Picker
A community forum user reports that since August 2026, fields newly inserted through the classic XML Mapping pane in Word report layouts show placeholder text instead of data, while older mapped fields keep working; the cause appears to sit in Word rather than Business Central. The author advises moving to the Word add-in data picker, available since 2025 wave 2 (BC27), which inserts fields through Add Data and avoids the legacy mapping layer.
post think about IT
"as of August 2026, newly inserted fields stop getting mapped. The content control shows the literal placeholder text instead of the value"
Key points
- New fields inserted via the XML Mapping pane stopped mapping correctly in August 2026, showing placeholder text instead of actual values
- The issue appears to be in Word’s XML mapping layer rather than Business Central itself
- The Word add-in data picker provides a cleaner alternative by inserting mapped fields directly without using the legacy XML Mapping pane
- The add-in approach represents Microsoft’s strategic direction for report layout development and avoids exposure to legacy mapping layer problems
- Developers should default to the Word add-in data picker for all new report layout work rather than waiting for the XML Mapping pane to cause more issues
Quotes
- “as of August 2026, newly inserted fields stop getting mapped. The content control shows the literal placeholder text instead of the value” (Identifies the specific regression affecting Word report layout development when using the classic XML Mapping pane)
Context
- Features: Word add-in data picker, Word add-in for report layouts, Add Data field insertion, conditional visibility controls
- Versions: BC27, 2025 wave 2, 2026 wave 1
Source: think about IT - Steven Renders, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.