Its quite a common requirement, that information of the user that is creating documents shows up within the document itself. (e.g. a “Best regards, firstname lastname” at the end of a quote).
This Step-By-Step describes how to add this relation to a template. In this example the Quote_base.docx template, that comes with the installation of DCP for CRM 2011,is used.

DCP-Client v5.27 or higher is mandatory!

More...

We have created a new function offering the user the possibility to show a dialog to pre-filter the result rows. This can be helpful if you want the user to select a specific related contact before starting to generatate the document.

This feature is available with version 5.26 upwards and only for DOCX-Templates.

Example:

Generate a quote and the user should select one of the contacts which should be taken to fill out the fields in the document.

More...

Protecting the generated document is a common question from our customers. With DocX and Macros it is very simple to achieve this

Open the template and add following Macro to the template and save it with the file extension .Docm.

Sub DCPMacro()
	ActiveDocument.Protect Password:="password", NoReset:=True, Type:=wdAllowOnlyReading, _     
           UseIRM:=False, EnforceStylelock:=False   
End Sub

This Macro will ensure that the created document is protected with a password.

The DCPMacro will be called after generating the document.

Other macros you could use are:

DocumentsCorePackMacroBeforeCreateActivity

DocumentsCorePackMacroAfterCreate

Example:

If you want that the Document Information Panel is visible you could add following macro which will be executed before the activity is created and saved:

Sub DocumentsCorePackMacroBeforeCreateActivity()
    With Application
        .DisplayDocumentInformationPanel = Not .DisplayDocumentInformationPanel
    End With
End Sub

Here is an example template for the entity account:

DocumentInformationPanel.docm (26.02 kb)

This is the 4th part of the series regarding the “Office Open XML”-format that is provided in DocumentsCorePack for CRM 2011. The template used in this video is the one that has been created in previous tutorials of this series, so its recommended to take a look into Part 1 – Creating a template and Part 2- Resolve Relationships first!

More...

This is the third part of the series regarding the “Office Open XML”-format. This video is based on the the results from Part 1 “Creating a template” , so I recommend to take a look into this demovideofirst.

More...

This is the second part of the series regarding the “Office Open XML”-format. This video is based on the the results from Part 1 “Creating a template” , so I recommend to take a look into this demovideofirst.

More...

This is the first part of a series regarding the use of the “Office Open XML (DocX)” format with DocumentsCorePack for MS CRM 2011.

The video shows how to create a Quote template showing a list of Quote-Products which is quite a common requirement.

Part 2 will contain a detailed description about how to resolve “Additional” relations like the Quote-> Quote Product relation used in this video.

This blog article gives you a short description on the different template settings available at the moment for DocumentsCorePack for MS CRM 2011.

CreateActivitiesFor:
If you don't want to add the activity into the Main-Entity (e.g. you are generating a quote and want to save the activities to the related contact or account.)
Select in the tree the related entity to which the created activity should be associated.

Syntax: Entityname, primarykeyfield. e.g.: contact,contact_contactid -> In this case the activity will be saved to the contact.

Additionalfields:
to read out additional fields (attributes) which are not defined in the document this means that those fields are loaded into the template automatically (e.g id-fields..). This is very helpful e.g to send emails via Documents Core Pack and you don‟t want the email adress to be shown on the template.

DocumentName: 
This setting predefines the name of the documents generated with this template. Its possible to use data from Fields out of CRM to be part of the document name. With this it is possible to generate the document name dynamically, based on constant characters and/or values of fields .
Constant characters have to be in single quotes.
To use field values in the DocumentName you have to write the fieldname ( schemaname ) surrounded by << and >>.
Some examples:

It is important that the inverted commas are also set!
Functions:
".pos(x,y)" will insert y signs from the xth position.
".left(x)" will insert the first x – signs
".right(x)" will insert the last x signs of the string

SaveTo Sub-Folder:
This setting predefines the name of the subfolder generated with this template. With this setting it is possible to save the generated document in a subfolder.
Its possible to use data from Fields out of CRM to be part of the subfolder name. That gives you the possible to generate the subfoldername dynamically, based on constant characters and/or values of fields .
Constant characters have to be in single quotes.
To use field values in the DocumentName you have to write the fieldname ( schemaname ) surrounded by << and >>.
Some examples:

It is important that the inverted commas are also set!
Functions:
".pos(x,y)" will insert y signs from the xth position.
".left(x)" will insert the first x – signs
".right(x)" will insert the last x signs of the string