The CRO wants a one-click quote PDF. You have three options: a Power Automate flow with a paid Word connector, a third-party document generator at six dollars per user per month, or a built-in Word template that ships with Dynamics. The built-in option is free, but it is also the option most teams give up on after the first week because the developer pane hides field bindings behind XML controls. Stick with it; the trick is process, not technology.
What Word Templates Actually Are
A Word template in Dynamics is a docx file with content controls bound to entity fields through the developer XML mapping. When a user generates a document, the platform replaces each control with the live field value, walks any related entities you exposed, and returns the rendered file. There is no server-side macro execution, no Office license requirement on the server, and no rendering quirks if your template stays inside the supported control types.
Build the Template the Right Way
Always start from a fresh upload, not by editing an existing template inside Word. The XML schema is generated when you upload, and editing offline can break the binding. Enable the Developer ribbon, choose XML Mapping Pane, select the entity schema, and drag fields onto the page.
Steps:
1. Settings, Templates, Document Templates, New.
2. Pick Word and the source entity.
3. Select related entities you want to walk in repeating sections.
4. Download the generated .docx, edit, then upload again.The first save cycle is the load-bearing one. Treat it like a build artifact and check it into source control as a binary asset alongside your solution.
Repeating Sections for Quote Lines
The most common shipping mistake is dragging a related entity column into a single cell instead of wrapping a table row in a repeating control. The result is a quote PDF that shows only the first line item. Wrap the entire row in a Repeating Section content control bound to the relationship, then drop the line columns inside.
[Repeating: quote_details]
| Product | Qty | Price | Extended |
[/Repeating]The repeating control is what tells the renderer to walk the collection.
Excel Templates and the PivotTable Trap
Excel templates work differently. They snapshot the current view as data, then apply the formatting, formulas, and pivot tables you embedded. PivotTables refresh on open in Excel, but only if the data sheet keeps the same column order as the original snapshot. Add or remove a column and the pivot loses bindings.
Lock the data sheet, hide it from users, and put all interaction on a presentation sheet. This keeps the snapshot stable and prevents accidental edits that break the next refresh.
Security and Personal Templates
Templates have two scopes: personal and organization. Personal templates are owned by a user and visible only to them and people they share with. Organization templates require the prvCreateDocumentTemplate privilege and are visible to anyone with read access to the source entity. Lock down organization template creation to a small admin team, or you will end up with eleven slightly different quote templates and no clear winner.
Versioning Without Losing the Binding
Templates do not carry through solutions cleanly. The recommended pattern is to export the template as a docx, store it in a Git repository alongside the solution, and re-import on each environment promotion. Tag the file with a version number in the template name visible to users so support can identify which version generated a given document.
Quote Template v3.2 (2026-04)When a user reports a layout bug, you ask which version the document footer references and reproduce against the matching docx.
Testing Across Word Versions
Templates render server-side, so the user’s local Word version does not matter for generation. It does matter when an admin downloads, edits, and re-uploads. Word for Mac and Word on the web both have content control quirks that can corrupt the XML mapping. Standardize on Word desktop for Windows for all template editing, and write that requirement into your governance doc.
What to do this week
Pick the one document your team generates most often, build a Word template the right way, and retire the manual copy-paste process behind it. Check the template into source control with a version in the filename and assign one owner to maintain it.
