You've correctly identified the core challenge: the absence of the XML Mapping Pane on macOS Word makes the standard Dynamics 365 Word template customization process impossible. Manually editing the XML directly is a valid approach, but you need to understand the structure and how Dynamics 365 expects the content controls to be defined.
Understanding the XML Structure:
When you create a Word template in Dynamics 365, the system generates XML tags within the document that correspond to the fields you want to display. These tags are embedded within "customXml" parts of the .docx
file.
Manual XML Editing Steps (macOS):
.docx
File:
.docx
file to .zip
.customXml
Folder:
customXml
folder within the unzipped archive.item1.xml
or similar. This file contains the data mapping information.<a:dataBinding>
, <a:xpath>
, and <a:prefixMappings>
. These elements define the mapping between the XML data and the Word content controls.xpath
attribute is crucial. It specifies the path to the field in the Dynamics 365 data source.<a:dataBinding>
element.fieldname
with the logical name of your Dynamics 365 field.r:id="rId1"
with a unique ID for the relationship.document.xml
:
word/document.xml
.document.xml
in VS Code.<w:sdt>
element (Structured Document Tag) to the location where you want the field to appear.fieldname
with the logical name of your Dynamics 365 field.w:xpath
value matches the a:xpath
value in item1.xml
.w:id
must be unique..zip
archive..docx
:
.zip
archive to .docx.
.docx
file to Dynamics 365 as a Word template.Important Considerations:
Alternatives (For Better User Experience):
Key Recommendations:
André Arnaud de Cal...
293,245
Super User 2025 Season 1
Martin Dráb
231,925
Most Valuable Professional
nmaenpaa
101,156
Moderator