It is possible to filter the linked entities of a 1:N and a N:N relationship during the merge process based on their IDs.This works in combination with DocumentsCorePack and AutoMerge, but only with .docx-templates.
Windows 8 has the WIF Framework built in, therefore our installers will fail for now trying to update the WIF on windows 8 clients.
Each product installs the following entities in CRM:
The features of the DocumentsCorePack [Print in Word]-button increase the performance and also the usability of our product.
The features allow you to select templates directly with the [Print in Word]-button.
To take adavantage of this feature you need at least the following version:
- DocumentsCorePack Server Version 5.25
- DocumentsCorePack Client Version 5.57
The below desribed methods are part of the ptm_dcp_custombuttonactions.js-web resource. More information on this resource can be found here. The comments and the code for one example of this resource are added below.
e.g., you can predefine a template that should be always used to perform the merge.
The following article contains a description of how to change, modify and extend this feature.
Starting with version 5.23 / TI and version 5.19 / DCP in combination with LicenseManager 5.2, the ribbon buttons will be disabled on perUser licensing, if the user is having the acccess flag for the product set to no.
Licensemanager 5.2 creates a new setting, IsPerUserLicense with value true|false when importing a licensekey.
In CRM 2011, all DocumentsCorePack templates are stored in custom entities. The name of this custom entity is DocumentsCorePack Template (ptm_mscrmaddons_dcptemplates).Every record of this entity has the template attached as a note.
Per default, CRM metadata information for DocumenstCorePack is stored here: