The latest version of DocumentsCorePack Server Based supports the population of metadata into SharePoint. Proper configuration of Dynamics 365 and DocumentsCorePack for the Dynamics 365 Integrate SharePoint is needed as well.

 Please note: Only base types are supported, taxanomy properties are currently not supported. ​

The below screenshot shows a property that was created by DocumentsCorePack
with data from Dynamics 365 (1).

Figure 1: Example of SharePoint Metadata
If you are not sure how to access the template settings to set the
SharePoint metadata, please have a look at this article first.

1. Access the SharePoint Metadata section
   

   

   Figure 2: SharePoint Metadata section
   
   
2. Add, edit or delete a property
   - To add a property use the [Add]-button (1)
   - To edit a property select an element (4) and hit the [Edit]-button (2)
   - To delete a property select an element (4) and hit the [Delete]-button (3)
   

   

   Figure 3: Add/Edit/Delete a property
   
   
3. Create a new property
   After you have selected Add/Edit the SharePoint Metadata Field Settings
   a window will pop up.
   You have to manually type the name of the SharePoint property. (1)
   How to create, change or delete custom properties on the Sharepoint is
   described in this external blog by Microsoft.
   The value of the property can be composed of Dynamics 365 fields and fixed text.
   More details about the supported syntax for this field can be found here.
   

   

   Figure 4: SharePoint Metadata
   
   
4. Save your template 
   Before you can use or test your template you have to save it. Either you save your template locally with the standard Save or Save as the functionality of Word or you use the Save template-option of the DocumentsCorePack client in order to publish the template to Dynamics 365.
5. Test your template [optional]
   As you have made changes to your template you might want to test it quickly. A step by step description of how to test your template can be found here.

The Hyperlink property allows you to define a pattern for a dynamically
created link. The following step by step description will show you how
to set this property in the DocumentsCorePack Client for your template.

Figure 1: Example of a dynamically created hyperlink

If you are not sure how to access the insert field option,
please take a look at this article first.

1. Use the Insert Computed item option
   

   

   Figure 2: Insert Hyperlink
   
   
2. Compose your link
   Select the Link-tab (1) and define your link pattern.
   The syntax for this field is described here.
   

   

   Figure 3: Link pattern in Link-tab
   
   
3. Compose your placeholder name
   Select the Display name-tab (1) in order to set a name for the link.
   Here we have a fixed text. The syntax for this field is described here.
   

   

   Figure 4: Display name-tab
4. Additional options [optional]
   You can enable the link to be displayed, even when there is no
   data returned for Dynamics 365 fields (1).
   Or you also can remove the link completely if there is no data returned (2).
   

   

   Figure 5: Insert Hyperlink (click image to enlarge)
   
   
5. Save your template
   

   Before you can use or test your template you have to save it.
   Either you save your template locally with the standard Save or Save as
   functionality of Word, or you use the Save template-option of the
   DocumentsCorePack client in order to publish the template to Dynamics 365
   

6. Test your template [optional]
   

   As you have made changes to your template you might want to test it quickly. 
   A step by step description of how to test your template can be found here.
    

The Computed Field property allows you to evaluate calculations of data from Dynamics 365.
The following step by step description will show you how to set this field in the
DocumentsCorePack Client for your template.

The example below shows an evaluated calculation based on Dynamics 365 field in a template (1). 


Figure 1: Example of evaluated calculation

If you are not sure how to get to the insert fields option
please take a look at this article first.

1. Use the Calculated Field document option 
   
   Figure 2: Insert Calculated Field
   
   
2. Create your calculation
   The syntax for this field supports the basic arithmetic operations.
   / -    divide
   * -   multiply
   +     summate
   -      subtract
   
   Other than the usual DCP syntax, numeric values are added
   without single quotes:
   
   Figure 3: Numeric values added without single quotes


3. Save your template
   
   Before you can use or test your template you have to save it.
   Either you save your template locally with the standard Save or Save as
   the functionality of Word or you use the Save template-option of the
   DocumentsCorePack client in order to publish the template to Dynamics 365.
4. Test your template [optional]
   
   As you have made changes to your template you might want to test them quickly.
   A step by step description of how to test your template can be found here.

Related Topics:
Insert a Hyperlink
Insert Fields
Insert an Advanced string
Insert QR-Code

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

The Advanced String property allows you to define a pattern for a dynamically
created string. The following step by step description will show you how
to set this property in the DocumentsCorePack Client for your template.

The example below shows an advanced string (2) based on placeholder
in a template (1).

Figure 1: Example of dynamic string

If you are not sure how to get to the insert fields option, please take a look at this article first.

1. Use the Advanced String option
   

   

   Figure 2: Insert Advanced String
   
   
2. Create your advanced string
   Define your link pattern (1).
   The syntax for this field is described here.
   

   

   Figure 3: Insert pattern for the Advanced String
   
   
3. Define a placeholder [optional]
   You can set a placeholder name (1) for your field so you find it easier
   in case you have to modify your template in the future.
   

   

   Figure 4: Define placeholder text
   
   
4. Save your template
   
   Before you can use or test your template you have to save it.
   Either you save your template locally with the standard Save or Save as
   the functionality of Word or you use the Save template-option of the
   DocumentsCorePack client in order to publish the template to Dynamics 365.
   
   
5. Test your template [optional]
   
   As you have made changes to your template you might want to test them quickly.
   A step by step description of how to test your template can be found here.

Related Topics:
Insert a Hyperlink

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

The example below shows a QR-Code (2) based on Dynamics 365 field
in a template (1).

Figure 1: Example of QR Code

1. Use the Insert Computed Item
   
   Figure 2: Insert QR Code
   
   
2. Create your QR Code
   Define your link pattern. The used text will be
   transformed into a QR-Code.
   The syntax for this field is described here.
   
   Figure 3: Define link pattern for QR-Code
   
   
3. Additional options [optional]
   The QR Code Level (1) shows the displayed level of the QR-Code. The default
   setting detects the smallest value. If e.g.: the value of this option is set with 5
   with a maximum sign-length of 108, then only 108 signs will be displayed.
   All signs that exceed the maximum length are cut.
   
   The Error Correction (2) defines the capacity and fault tolerance of the
   QR-code. The value shows the amount that can be restored in percent.
   
   The available options are:
   - Level L =7 % of the code words/data can be recovered
   - Level M = 15 % of the code words/data can be recovered
   - Level Q = 25 % of the code words/data can be recovered
   - Level H = 30 % of the code words/data can be recovered
   
   The Max Length (3) is not editable and depends on the above settings.
   
   Figure 4: Additional options
   
   
4. Save your template
   
   Before you can use or test your template you have to save it.
   Either you save your template locally with the standard Save or Save as
   the functionality of Word or you use the Save template-option of the
   DocumentsCorePack client in order to publish the template to Dynamics 365.
   
   
5. Test your template [optional]
   
   As you have made changes to your template you might want to test them quickly.
   A step by step description of how to test your template can be found here.

Related Topics:
Insert a Hyperlink
Insert Fields
Insert an Advanced string

and the final merged document with also the sub template merged(2). 

Figure 1: Example of a sub template

If you are not sure how to get to the insert fields option,
please take a look at this article first.

1. Use the Insert Static Item option
   

   

   Figure 2: Insert Static Document
   
   
2. Select a document to insert
   At this point, you have two options. You can either select a sub template and
   provide the necessary field as a merge parameter or you can skip this step and
   select a static document only (which does not require a parameter for merging).
   
   a) Provide a merge parameter [optional]
   Select an ID-field from the treeview (e.g. Contact) (1) and check the
   Provide the selected field as a parameter - checkbox.
   

   

   Figure 3: Provide a parameter
   
   b) Hit the [Select Document]-button
   

   

   Figure 4: [Select document]-button
   
   c) Select a sub template or static document
   All the available documents are stored in the DocumentsCorePack templates entity.
   

   

   Figure 5: Document selection (Look-up window)
   
   

3. Insert place holder
   You will notice the name of the select template in the new window (1).
   Apply the new field by clicking the [OK]-button (2).
   

   

   
   Figure 6: Template added
   
   Save your template
   

   Before you can use or test your template you have to save it.
   Either you save your template locally with the standard Save or Save as
   the functionality of Word or you use the Save template-option of the
   DocumentsCorePack client in order to publish the template to Dynamics 365.
   
   

    

4. Test your template (optional)
   As you have made changes to your template you might want to test them quickly.
   A step by step description of how to test your template can be found here.
   

Sometimes you may be asked to create a new settingskey for one of our products (e.g. if we developed a customization for you or if a special configuration is needed, etc.).
To do so, please follow the six easy steps below.

Add-ons: AutoMerge, DocumentsCorePack, TelephoneIntegration

How to create a SettingsKey manually in MS CRM 2013 or CRM 2015, step-by-step description

1. Open CRM in the InternetExplorer.

2. Navigate to Settings within the CRM navigation. 

Figure 1: CRM Settings in the navigation

3. Within the settings, navigate to MSCRM-ADDONS.com Products in the Extensions-area of the sitemap.

Figure 2: MSCRM-ADDONS.com Products in the CRM settings

4. Open the product record for which you need to create a new settingskey for with a double-click on it.

Figure 3: View of MSCRM-ADDONS.com Products

5. A new window opens. Within this new window, navigate to the MSCRM-ADDONS.com settingskeys in the menu on top (see Figure 4) and click on the [Add New MSCRM-ADDONS.com Settingskeys]-button (see Figure 5).

Figure 4: View of MSCRM-ADDONS.com settingskeys-menu

Figure 5: View/add settingskeys of/to  MSCRM-ADDONS.com products

6. A new window opens. In this window, you have to define the name of the settingskey in the Name-field and the value (true) in the KeyValue-field. Once done, save and close your settings. 

Figure 6: Create a new settingskey for MSCRM-ADDONS.com products

Please note: If the new key is intended for a client application like DocumentsCorePack or TelephoneIntegration, you need to restart the Client application. Otherwise, the setting will not be applied to the Client.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

+++++++++++++++++++++++++++++++++++++++++++++++++++

   Please note: This article applies to CRM 2013 as well as to CRM 2015/2016

+++++++++++++++++++++++++++++++++++++++++++++++++++

When ordering licenses, you will be asked for the Organisation Unit Name of your CRM system.
This information is mandatory in order to create a license. Below, you will find a short description on how to get the necessary information for CRM 2013 and CRM 2015/2016. Please click here if you need some information on how to get the UON in Microsoft Dynamics 365. 

Open you CRM in your preferred browser and navigate to Settings.

Navigate to Customizations and Developer Resources.

Here, you will find the Unique Organization Name.

Please note: For CRM 2013 as well as CRM 2015/2016, the Unique Organization Name is required.
Besides, our key is case sensitive and does not work if the names do not fit.

This is where you find the Unique Name in CRM 2013:

This is how it looks like in CRM 2015/2016: 

Figure 4: Unique Name in CRM 2015/16

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

This chart applies to DocumentsCorePack client versions 5.84 or higher,
DocumentsCorePack server version 5.41 or higher and AutoMerge versions 5.32 and higher.