The Document Template functionality in Dynamics 365 is useful as it allows you to create business branded documents using information from the Dynamics 365 system. It does have some limitations which I feel let it down and prevent it from being able to do more complex documents, such as limiting the number of entities you can drill through, however, it can still be useful in some scenarios.
To create a new Document Template, go to Settings -> Templates -> Document Templates. In this post I will be making a new Word document template for the Quote entity.
Creating a new Quote Word Template
Once you have selected the entity to work from, you will be prompted to choose the relationship details to include, for this example I have included the Quote Line (quote_details) 1:N relationship and the User (system_user_quotes) relationship.
Selecting the relationship details to include in the document
After selecting the relationships that should be included in the document, click on the ‘Download Template’ button and a new Word document will be downloaded.
Whilst within Word the XML Mapping Pane is used to insert the fields into the document. This option is available under the Developer tab, which may need to be enabled if you have not used it before.
Displaying the XML Mapping Pane
The XML Mapping Pane needs to be changed to show the fields from Dynamics. To do this, click on the drop down box for the Custom XML Part and change it to the CRM record.
Changing the Custom XML Part
Once the XML Mapping Pane is using the correct Custom XML Part you will be able to see the fields from the Quote record. To insert these fields into the Word document, click where you would like the field to be entered and then right click on the field in the XML Mapping Pane, select Insert Content Control and then select the field type (I usually use Plain Text as I have found that Rich Text can cause Word to crash).
Adding field to the Word Document
This step can then be repeated as many times as needed to include all the information you want in the Word document.
As I am working with a Quote in this example, I then wanted to add the line items to the document. This is in done by first creating a normal table in Word.
Adding fields & a normal table
After the table is inserted, select the row which should repeat and then go to the XML Mapping Pane and find the repeating section, right click on it and then select Insert Content Control and Repeating. This will then make that row a repeating section, you can tell it has worked correctly because the row changes slightly to include an outer box.
Setting the row to repeat
Row display after being made a repeating row
You can then add the fields to the individual cells in the same way that you would add the field to the document. In this example I produced the table below.
Repeating row with fields from Dynamics
Once the template has been finished, it can be uploaded to the system and made available to the users by going to Settings -> Templates -> Document Templates and then selecting Upload. Once the document template has been uploaded the system will take you to the details page.
Details for the Document Template
To then run the document template, go to a quote and select the 3 dots in the menu bar, then go to Word Templates and select the appropriate template. The Word document will then be downloaded with the information from the record.
Using the Document Template
Finished Word Document
Original Quote & Quote Details
Original Quote that has been used
Original Quote Line items that have been used
My frustrations with Document Templates
Whilst the custom document templates are useful there are some frustrations I find when using them.
Updates to template
After the Document Template has been created, it seems to be difficult to update the relationship with Dynamics. For example, if a new field is added to Dynamics after the template has been generated, it appears that the only way to update the field list is to go into the XML of the document and manually add in the required fields. This could be daunting if the person updating the document does not understand XML. Alternatively, a new document would need to be generated and the content of the template copied over manually, this would be prone to errors and cost more time each time an update is needed.
Direct Relationships Only