- Blog


This blog is deprecated since July 2020.The articles below are no longer maintained and might contain outdated information. 
You can find the most acutal and relevenat information in our Knowledge Base at Blog


Hello and welcome to our blog! What can we do for you? Are you looking for further technical information or step-by-step instructions to our products? Or would you like to read the latest news on mscrm-addons? Please feel free to browse our blog for detailed information and to share our posts!

Analyze Template Feature (Dynamics 365)

The Analyze Template Option will be executed automatically before you save a template back in your Dynamcis 365 system with the latest version of the DocumentsCorePack Client (9.37 or higher). Additionally it can be executed on demand while designing a template by calling it from theTemplate Explorer window. 
The warnings are just an information and no actual errors. False positve can occur but can be simply ignored.
You can turn this feature of by disabling this functionality. How to disable this is describe here: Template Explorer Settings

Details ab the functionality will be added shortly to this blog article, so please check again in a few days. 

Step-by-Step: How to generate documents in Power Automate (Microsoft Flow)

Power Automate is becoming more powerful every day and potentially is about to replace the long-standing classic Dynamics 365 workflows. In this blog, we will present and showcase how DocumentsCorePack allows us to generate and process documents within Power Automate (Microsoft Flow).

How it works:
When using DocumentsCorePack every document that has to be generated is defined by a record of an entity called “AutoMergeWorkingItem”. This record holds all mandatory definitions to generate the document: 

1. Record to use:  What record should the document be generated for (e.g. account, quote, etc.)
2. Template to execute: ​ Defines the DocumentsCorePack template that should be used to generate the document.
3. Output format: ​The Filetype the document should be generated and returned as Pdf, docx, Html. 
4. (Optional) Processing settings: This is not a necessity but DocumentsCorePack allows to not just generate a document but also process the document by definitions on the AutoMerkeWorkingItem record (e.g. Print, Save to SharePoint, Send for e-Signing, etc.). 

Once such an AutoMergeWorkingItem is created, the DocumentsCorePack service will generate the document and deliver it back as an attachment to this record. It becomes clear that in order to generate a document within Flow the only thing that needs to be done is to “Create an AutoMergeWorking Item Record”.

Note: The mandatory parameters required can be brought into flow in various ways. E.g. you could build a Canvas App that passes the parameters to the Flow or you can simply use the Common Data Service or Dynamics 365 connectors within Flow to load them (see figure below).


Step-by-Step: Create an AutoMergeWorkingItem in Power Automate (Microsoft Flow)
Now that we know what is needed: Let’s take a look at how such a document generation request has to look like.

Our use case is to generate a quote document in PDF – format upon activation of the quote.

Note: In our scenario, we are using the common data service connector. Especially with the October 2019 update for the “Common Data Service (current environment)” it became a lot easier to do certain things like creating records. I want to emphasize though that it's of course also possible to use the Dynamics 365 connector.

1. The Trigger of the flow: In our scenario, the flow is defined to trigger a change of the status field of the quote entity as follows:


What’s important: We will need the context of this step as it defines the record our document needs to pull the data from. So we have the first required parameter: The record to use!

2. Get Template to execute: Here we use the Common Data Service- 'Get Record' action to load our template. Since we always want to use the same quote-template we make it simple and “hardcode” our template. 

So what do we have here? Where does this GUID in the item identifier come from? To answer this we have to know that every template designed with the DocumentsCorePack Template Designer is stored as a record of the “ DocumentsCorePack Template” entity. As can be seen on the screenshot this is the entity we are getting a record of.

You can e.g. open the template record you want to use and copy the GUID from the URL as you can see below. 


To summarize: This 'Get Record' step will provide us with the second parameter: The template to use! As we also know that our output format should be PDF we are all set to finally define our document generation request! 

3. Create AutoMergeWorking Item: As all parameters are now clear we can use the Common Data Service – Create Record action to create our document generation request as follows: 


We create a record of the Entity “MSCRM-ADDONS.COM AutoMergeWorkingItem” and choose the Action to be “Create Document”. We can also give it a name that is quite handy to maybe later identify and review the documents generated via this Flow. Now we need to set our parameters:

a. Record to pull data from (PrimaryRecordUrl):


This is kind of challenging at this point. We did copy the URL of a quote we opened in Dynamics and replaced it with the “Quote”-parameter (Unique identifier of the quote from our Flow-Trigger action). 

b. Template to Execute (TemplateToExecute):


Here we reference the Unique Identifier parameter of our “Get Record” step where we did load the template above. 

c. FileType (SaveAs Value): This is a simple one – we simply select “PDF” from our picklist. 


And that’s it! We did it. So every time a quote gets activated we will now get a document generated.

Next steps: Naturally you want to do something with the document once generated. As outlined above you can either use the AutoMergeWorkingItem to process the document but you can also process the document within your flow. The generated document can be found on the AutoMergeWorkingItem record -> Created Document section.

 Note: This field will be filled when DocumentsCorePack successfully created the document. You will have to wait for the AutoMergeWorkingItem record to become “inactive”. This tells you that the document is ready. 



That's it! We appreciate your feedback! Please share your thoughts by sending an email to

Dialing Rules

When configuring DIALING RULES we need to know exactly how the number must be concatenated for dialing

- internal company calls ( the call is not routed outside your local loop)
- local calls within your area code
- for long distance calls within your country but outside your area code
- for international calls outside your country

To properly set those, we need to know the following codes like 

"exit code", "country code", "area code", "trunk code", "access code".

First of all, we need to define what is our 
* country code -> Country calling codes are used to dial phone numbers internationally. Each country has an assigned code of its own. In order to dial an international phone call you must always use a country code before the actual subscriber telephone number.
* exit code -> Exit codes, also known as international access codes or international direct dialing (IDD) codes automatically redirect telephone calls to a foreign country. It is the first code you dial when calling abroad. You may replace it with the plus sign (+).

This setting depends on the country you are in.
For example if you are located in United States, your Country Code is 1 and the Exit Code is 011.
If you are located in Germany, then your Country Code is 49 and the Exit Code is 00.
If you are located in Australia, then your Country Code is 61 and the Exit Code is 0011.

Exit Code is a sequence of digits you need to dial for international calls. If a person in Australia wants to call into Germany, then they must dial their own Exit Code 0011 and the Country Code of Germany 49.

For non-international calls, we need to define what is the 
* TrunkCode 
and what the 
* local AreaCode.

National TrunkCode is used to place calls within a certain country. It is the sequence of digits that must be dialed before the Area Code. It is left out when dialing in from abroad.
If you are located in United States, then your Trunk Code is 1.
If you are located in Germany, then your Trunk Code is 0.
If you are located in Australia, then your Trunk Code is 0.

*Access Code is code dialing for accessing phone lines outside your companies phone network. Regardless if you want to make an international call or noninternational call. If the call is internal between the local companies extensions, then the Access Code needs not to be dialed, since there is no need for accessing outside phone netwoork.

For more help please check this side ->

The sintax for internation calls is 
[Access Code] + [Exit Code] + [Country Code] + [Area Code] + local subscription number 

The sintax for long distance calls is 
[Access Code] + [Trunk Code] + [non-local Area Code] + local subscription number 

The sintax for local calls is 
[Access Code] + [Trunk Code] + [local Area Code] + local subscription number 
or if the local area code is not required
[Access Code] + local subscription number 

The sintax for internal calls between the local company extensions is to dial only the internal extension (usually not longer than 4 digits).

To set those settings you need to define the Dialing Rules in Phone and Modem settings. 
If you have troubles succesfully dialing the numbers over our CTI, you need to pass us the syntax form for 

  • international calls
    [Access Code] + [Exit Code] + [Country Code] + [Area Code] + local subscription number 
  • for long distance calls
    [Access Code] + [Trunk Code] + [non-local Area Code] + local subscription number 
  • for local calls
    [Access Code] + [Trunk Code] + [local Area Code] + local subscription number 

To verify the settings go into TIClient / Setup / Phone tab. 

After you press the Apply button, those settings will be stored in the Windows LOCAL_MACHINE registry

Note: Because the registry branch Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\Locations\Location has restricted permissions for modifying values, you might need to apply those settings via the official Windows Phone and Modem (telephon.cpl) tool. 
Otherwise the changes you made in the TIClient  / Setup / Phone / Dialing Rules, will not be saved. 

How to import, export & transfer templates using the DocumentsCorePack Online Service Configuration

This blog article outlines how to import, export and transfer templates using the DCP online service configuration.Our DocumentsCorePack (DCP) Online Service Configuration allows users to configure DCP easily online. For further information on how to configure DCP Online, please have a look at our DCP Online Configuration video. 

The DCP Online Config offers lots of useful functionalities, such as for example import, export and transfer templates. This step-by-step tutorial outlines how to use them properly.

1. Login to, go to My Account and then My Cloud Service. 

2. Select the ❶ service that you want to import/export your templates from and click on the  [import/export documentscorepack templates]-button . 


3. This opens the Template Management-window, which allows you to import, export and transfer templates as you can see below.


Import templates 
Please click on the [Import]-button if you would like to import DCP templates. You may select multiple *.docx/ *.docm/ *.dot templates or *.zip file containing multiple templates. You can also drag and drop files form the explorer to this dialog. Furthermore, you will be asked to specify how to proceed with the templates you import, if that already exists in the system. You have the possibility to select between the following three options, as you can see in the figure below. These options are also available if you want to transfer a template. 


1) Overwrite
The template GUID stays the same. 

2) Create new
The 'old' version will be kept with the 'old' template GUID and the 'new' version of the template will be imported with a 'new' template GUID. 

3) Skip 
All existing templates will be ignored. Only new templates will be imported.

 Export templates
Please click on the [Export]-button in order to export all DCP templates as .*zip-files.

❸ Transfer templates 
You have the posibility to move templates to another organization. Select the organization where you want to transfer your templates to and click on the [Transfer]-button. If a template already exists, you can choose as explained before between overwrite, create new and skip. 

IMPORTANT: Should the templates not be extracted correctly, make sure you do not export to a folder that has a lot of subfolders. The maximum length should not be over 260 characters. 

Correct folder structure for exporting:

Incorrect folder path for exporting:

That's it!
 We appreciate your feedback! Please share your thoughts by sending an email to

DocumentsCorePack Template Import Manager

This blog article outlines how to install and use the DCP Template Import Manager. Please notice: This blog article is intended for On-Premise version and DocumentsCorePack local intallations. If you are using the online version, please have a look at this blog article. 

If you are using the latest version of DCP, you will find the DCPIE (highlighted in yellow) in the install directory, which allow you to easily import, export or transfer templates from a source organization to a target organization.


Open your DocumentsCorePack install directory and select the TemplateImportManager.  A double-click on the application opens the Template Import Manager dialog, which allows you to either import, export or transfer your DocumentsCorePack templates. These three options will be explained below: 


Next, double-click on the [Load from Zip]-button and open the directory containing your Zip-file – “Export” in this case. 


Next, open your Zip-file and select the templates you want to import. It is possible to ”Select All” or single templates from your Zip-file by checking the corresponding checkboxes on the left side. Click on the [Import selected templates]-button to finish the Import. 


Export from Zip
Hit on the [Export from Zip]-button to export DCP templates. Here you have to specify a connection to the organization from where you want to export your templates. Like explained before, select an existing profile, click on the [Retrieve all]-button, select the source organization you wish and hit on the [OK]-button.


​As mentioned before, double-click on the [Load from Zip]-button and select the templates you want to export by selecting all or only single template from your Zip-files. Click on the [Export]-button to finish the Export. 

Transfer to organization 

The third option allows you to transfer DCP templates from a source organization to a target organization. Therefore, please select the source and the target organization, like explained before. Next, select the templates you want to transfer and hit the [Transfer]-button.



The TemplateImportExportConsoleApplication does the same as the TemplateImportManager – it automates the actions: import and export.

Therefore, please open your cmd from the Start pane or by pressing the Windows key + R. Next, search for the DCPIE.exe and enter the command help. This action displays you a list of parameters which are needed to perform the necessary actions as you can see in the figure below.


Export/import templates via the DCPIE
The following scenario explains the syntax of an export process. If you want to export templates and handle the necessary arguments by yourself, you need to use the params argument, which indicates that you are providing these parameters. The function looks like in the figure below: 


The arguments in the export scenario are the following:

  • Connectionvariant:

o    Parameter:
action: Defines which operation should be performed (allowed are  „import“ and „export“).
You can find the profile ID in the registry under the following path: HKEY_LOCAL_MACHINE\SOFTWARE\PTM EDV-Systeme\Profil

connectionvariant: Defines how to connect to Dynamics 365 (allowed options are: params, registry and dialog).
o    Registry: You have to enter your profile ID here.
o    Dialog: Opens the default CRM connection dialog.

Only if the connectionvariant is “params” you will need the following additional parameters.

  • Server: dyn365srv2:555
    This is the Dynamics 365 server on which you want to perform the actions.
  • Connectiontype: standard
    Here you have the possibility to choose between standard, online and hosted
  • Organization: ptmedvsystemegmbh
    Enter the name of the organization you want to use.
  • Action: export
    You can choose between export, import and transfer.
  • Exportdirectory: c:\users\administrator\desktop\myTemplates
    Please specify here the directory which serves as destination for your exported templates.
  • Username: mpoelzl@ptm-edv
    This is the username you use to login to Dynamics 365.
  • Password: xxx
    Please enter your secret password here.


The example above showes the syntax for the export functionality. The import functinality shares the same syntax with the export functionality, except that the parameters zip and zippath are removed. The parameter exportdirectory is replaced with templatefolder. ​

In the templatefolder parameter you need to specify the folder which contains your templates. And there also is a new parameter called mbresult.

Mbresult: Valid options are Yes or No.

This indicates that all templates should be overwritten if they are already existing.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to


Master Template

The Master template feature  allows you to manage the design of documents header and footer in a separate templates. So when the design changes you have to modify one template instead of each template. In your actual templates you just have set the master template which should be applied when the document is merged. This feature requires at least version 9.27 of the client and version 2017.193 of the server or service. 

Example: The template Account reconnected has set the Master Template PTM 

The created document contains the companies design in the header and footer.


Figure 1: Example 

1.       Set up your Master template for your company
Open a plain word document. 
Edit the header and footer according the companies design.
Save the document by using the Save template-option as a static template in your Dynamics 365.


Figure 2: Example Master template

2.      Assign the Master template to your normal templates
Open the template settings and go to the Master template setting on the General tab (1).
If you are not sure how to get to access to the template settings to set the
document subject please have a look at 
this article first.

You will find two settings in the Master Template group.
With the first setting Header/Footer (2) you can define which Master template should be applied for all header and footers in the document. The setting Separate Footer is optional if you want to set a different Master template for the footer.
To assign a Master template you can either type in the name of the Master template or click on the button to open the lookup dialog.


Figure 3: Master template settings

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
a 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 

- Design also the first page and even/odd header/footers in the Master template otherwise those sections will be blank in the result document  
- The size of the header/footer in the Master template shouldn’t be bigger than the page margin of the main template. Otherwise it will shrink the document body size in the output document. There is no setting to limit the size of the header/footers.

- Format styles of the Master template are not merged into the main template. Text formatting made in the Master template without the use of format styles will be displayed correctly. If you like to work with format styles in the Master template please make sure that they exists in each template. 

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to


DocumentsCorePack Print Application Configuration for Dynamics 365

This blog article outlines how to configure the DocumentsCorePack Print Application for Microsoft Dynamics 365. More information about how to install the DCP Print Application can be found here

Please notice: The DCP Print Application is intended for small local printer installation. It does not work on servers with multiple printers. In this case, it is recommended to use DCP ServerBased where the services are better managed. For further information, please contact our support team. 

DCPPrintService Configuration
After finishing the installation, the DCPPrintService Configuration window opens. This window provides you with different tabs to configure your DCP Print Application as you can see  in the figure below highlighted in yellow. 


1. The General-tab
The General-tab provides you with the opportunity to set the general settings of your future service (see figure above). You have the possibility to activate debugging, set a batch delay  (90 seconds is set per default, which is the delay between the service checking for new print jobs).

You can also add & remove printers, that your application will use.

​2. The Printer-tab
The Printer-tab provides you with the possibility to create a new configuration, edit an existing one, copy a configuration and change the settings and also to delete configurations.


In order to create a new configuration, click on the [New]-button in the Printer-tab, highlighted in yellow.

This action will open the following dialog.  Here you have to:

Specify a configuration name to be able to create a printer configuration. The configuration name (highlighted in yellow below) consists of printer@username (the user which has access to the local printer) + computer name (the computer on which the service is running)

Select the printer from the drop-down menu. You can only use the printer created with your user and your machine.

Hit the [Save & Close]-button.


After saving, you will see the saved printer configuration in the Printer-tab. 


The saved printer configuration is also automatically added in the General-tab in the Filter-area (see in the figure below). To remove a printer, please select it and click on Delete on your keyboard.

3. The License-tab
The License-tab enables you to quickly check your license state. If the license is invalid, the service will not start. For more information on the license manager, please have a brief look at our Licensing Guide.

4. The Log-tab
The log prvides an excerpt of the DCPPrintService event log, filtered for this specific service. This helps you to identify any issues with the service. 

​That´s it! 

Hit the [Save & Close]-button in order to finish the DCPPrintService configuration. You will now find the DCPPrintService in your system tray. Right-clicking on the icon brings up a context menu, allowing you to connect to a different organization, open the config, restart the service or quit it.

The installer also adds an autorun entry to your local user account, starting the DCP Print service with your windows.


If you now hit the [Create Document]-button, the DocumentsCorePack Dialog provides you with the new “Print document”-option, where you are able to select the printer you have configured before (highlighted in yellow).

Please notice: You can configure as many local printers as you like.


That’s it! We appreciate your feedback! Please share your thoughts by sending an email to


How to disable the user button order configuration for SmartBar

If you need a static order of the buttons in the SmartBar Ribbon,
disable the „Enable Drag Option“ in the CRM > Settings > SmartBar > General Settings:


Afterwards delete the user specific button order in the CRM > Settings > SmartBar > Global Settings:

 Global Settings


That’s it! We appreciate your feedback! Please share your thoughts by sending an email to


Display rules for One-Click-Actions

This blog article outlines how to add display rules for One-Click-Actions. The purpose of display rules is that users only see One-Click-Actions that are relevant to them.

More information about how to configure a One-Click-Action can be found here

Please open your Dynamics 365 Settings, navigate to MSCRM-ADDONS-section and select DocumentsCorePack. In the main configuration window please go to the One-Click-Actions-tab. Select the entity for which you want to configure the one-click-action (in this case Contact) and hit the [Edit]-button. 

In the so opened window, you are provided with all one-click-actions for the entity Contact. With a klick on the [+]-button on the right side, you can add a display rule for your one-click-action.

Display rules via security roles
In this example, we want to assign the "Send  quote to customer via email" OCA to a security role by hitting the [+]-button. 


​In the window below, please select the security role that a user has to have to see this one-click-action. In this case, we select Customer Service Representative as you can see highlighted in yellow below. ONLY users with this security role will be able to see the OCA. If nothing is selected everyone will see the one-click-action. 

​Display rules via field values 
You also have the possibility to  add additional conditions as display rules. Therefore, please hit the [Advanced]-button at the bottom of the window above.  Here you can find all attributes of the entity Contact. In this example we select Status and Active from the drop-down menu, which means that this OCA will ony be shown for contacts that are active as you can see in  the figure below. 
Please notice:If in addition to a field condition a security role is selected they are considered to be of type "AND", which in our example, means that only Customer Service Representative with the status Active can see this one-click-action. 

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to


TelephoneIntegration Phone Test Tool

This blog article guides you through the test of the compatibility of your phone system with the TelephoneIntegration addon for Microsoft Dynamics 365. For more information, please also have a look at the corresponding documentation

The tool offers two communication channels. You need only one of them to be able to use our CTI.

For testing, via TAPI you require a valid TAPI driver from your phone system vendor.

​Via SIP
For testing SIP protocol, you need a valid sip user account. For this, you require SIP username, SIP password and SIP domain (PBX server).

The testing consists of 7 steps you have to follow:
1. The tool can be downloaded and downloaded from our website.
2. After the extraction, start the PhoneTest.exe.
3. Select your desired channel of communication (TAPI or SIP).
4. Test an incoming call.
5. Test an outgoing call.
6. Evaluate the results.

​Step 1: Download and start the tool
​First, please download the ZIP file here, extract and open it by hitting the PhoneTest.exe file. Start the tool and press the [Get Startted]-button. 

Step 2: Select the plugin 
Next, please choose the plugin interface you want to test.


Step 2: Configure plugin  
If selecting TAPI, you need to select your TAPI line provided by your TAPI driver and hit the [Next]-button. Please note: If the selected line cannot be activated, the [Next]-button will stay disabled.


If selecting SIP, you need to type in your SIP credentials – your username, password and the domain as you can see below.


Step 3: Grant access
In the firewall-window please grant access to the phone test tool as you can see in the figure below. ​


Step 4: Test incoming call
After successful registration with your SIP user account, you can now test an incoming call. Hit the [Continue]-button in order to do that.


Accept or decline the call by clicking one of the buttons.


At the bottom, you will find enabled features listed that were successfully tested.


Step 6: Evaluation of all inocoming and outgoing calls
In the end, we evaluate the incoming and outgoing call. We check if the caller/caller number was detected if the Answer/EndCall operation is possible and if we can observe the state of the call. If everything is green, then the TelephoneIntegration addon is compatible with your phone system as you can see in the figure below.


​That’s it! We appreciate your feedback! Please share your thoughts by sending an email to