++++++++++++++++++++++++++++++++++++++++++++++++++
Please note:
This article applies to ActivityTools in
Microsoft Dynamics CRM 2015 and 2015/2016 ONLY!
++++++++++++++++++++++++++++++++++++++++++++++++++

Step-by-step description on
how to activate debugging for ActivityTools

1) To activate debugging for ActivityTools open CRM and navigate to Settings:

 
Figure 1: CRM > SettingsThere, open the Solutions. 
 
Figure 2: Solutions

Search for ActivityToolsPluginCore and open it with a double-click:

 
Figure 3: Search for ActivityToolsPluginCore

2) This action will open the ActivityTools Settings. In the settings, select the General Settings-tab and enable debugging. 

 
Figure 4: Activate/deactivate debugging for ActivityTools in CRM.

Click on the [Save Configuration]-button in order to save your settings. Debugging is enabled now.

3) Next, access the log files. The log files are usually stored in the MSCRM-ADDONS.com Debug-entity. the easiest way to access it is by using the Advanced Find.

Figure 5: Advanced Find in CRM 2015 

4) Settings for the Advanced Find: Select the MSCRM-ADDONS.com Debug-entity and include the following condition: Name must Contains PTMActivityTools. This ensures, that only ActivityTools-files will be retrieved.

Figure 6: Settings for Advanced Find

5) Next, click on the [Edit Columns]-button and the below editor will open.

Figure 7: Edit columns editor

Use the Add Columns-functionality to add the ptm_message-field to the grid. Click on the [OK]-button in order to proceed.

 
Figure 8: Add Columns-functionality

6) Back in the main dialog, click on the [Results]-button. Next, delete all retrieved debug records.
Another way is to select the debug file by Created On date. Then reproduce the error and refresh the result list of this Advanced Find. This ensures, that you only receive the latest and relevant log files. Select all records and click on the [Export MSCRM-ADDONS.com Debug]-button.

Figure 9: Export MSCRM-ADDONS.com debug-files

In the next dialog, check Static worksheet ... and click on the [Export]-button. 

Please send the Excel log-file with a short error description and a screenshot to our support address support@mscrm-addons.com

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

This blog describes how to add a language to DocumentsCorePack ServerBased Dialog. Per default, English and German is provided.

Requirement: DocumentsCorePack ServerBased Dialog

Step-by-step description:

1) Open CRM and navigate to Settings:

Figure 1: Settings   

In the extension, navigate to Customization 

Figure 2: Customization

There, click on Customize the System

Figure 3: Customize the System

2) The Web Resources-window appears. There, click on Web Resources in the tree-view on the left and select ptm_dcp_dialoglocatlization.xml on the right with a double-click.

Figure 4: Web Resources window in CRM

3) In the window that opens now, click on Text Editor or on the URL.

 
Figure 5: Text Editor version of the German XML language file.

4) Next, copy the whole Web Resource content into any editor starting with to . Replace the LCID with the apropriate LCID. 1033 is, for example, French for France. Click here to get an overview no different Locale ID Values. 

It should look like following:

…..
…..
…..

5) Once the translation has been finished, save the new file locally.

6) Next, create a new Web Resource and name as you wish.

Figure 6: Create a new web resource

7) Then publish your settings 

Figure 7: Publish your settings

8) Next, a new SettingsKey needs to be created. To do so, go back to the Settings-area in CRM. Within the Settings, go to MSCRM-ADDONS.com Products and select AutoMerge. 

Figure 8: MSCRM-ADDONS.com Products in CRM

9) Now click on the drop down next to AutoMerge in the main navigation area and click on MSCRM-ADDONS.com Settings Keys.

Figure 9: Drop down menu next to AutoMerge

10) Click on the [+ADD NEW MSCRM-ADDONS.com SettingsKey]-button.  

Figure 10: Click on [+ADD NEW MSCRM-ADDONS.com Settingskey]

Please enter CustomLanguageFileWebResourceName as Name* for the new Settingskey and type in the name of the WebResource you have created in step 6 in the KeyValue

Figure 11: Enter Name and KeyValue

11) All that is left to do, is to click on the [Save and Close]-button in your settings.

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

This blog article explains how to add related detail fields to be shown in the TelephoneIntegration (TI) balloon via FetchXML-feature.

How does it work?

The standard TI Configuration only shows fields from the same entity which can be configured via check boxes in the Server Config. 

Figure 1: Standard balloon caller information

TI Server will be equipped with an option to supply one FetchXML command with a GUID placeholder. This placeholder will be replaced with the corresponding entities ID, if a match is resolved.
So we receive 2 groups of detail fields - the original fields (from the originally resolved entity) and related fields (from the related entity).

Figure 2: Additional Fetch result

In our example, we use Contact plus full address. In order to add additional related fields from a different entity, a FetchXML has to be executed.

Therefore, TelephoneIntegration Server and Client need to be updated to the latest version.

Requirements
TelephoneIntegration for MS CRM 2015
Server version: v. 2015.5 or higher
Client version: v. 7.7 or higher

 

How to add related detail fields to the TI-balloon?

1) First, make sure that you use TI-Server v.2015.5 or higher. If so, please proceed with the next step. If not, download the latest TI Server version. 
Once the update has been finished, you will see the following organisation overview. Here, select the appropriate organisation and click on the [Launch config]-button.

 

 
Figure 3: TelephoneIntegration Organisation overview. 

2)  The following window appears. Check the entity you would like to work on (here: Contact) and then click on the [Fields]-button that appears next to the entity. 

 

Figure 4: TelephoneIntegration Server Config. 

3) Now the following window appears. In this window, users can specify the details that should be shown with this entity. 

Figure 5: Fields details for default TI balloon caller information.

Please note: It is possible to display up to three result fields per resolved record! If additional information from related entitiy is needed, the FetchXML is executed and additional fields are added.

In our example, we also want the FetchXML to return the ticket-number from the last created active case (if the resolved contact is stored in the customer field).

4) To do so, please click on the [Supply custom FetchXML]-button (highlighted in Figure 5)

5) In the newly opened window, please add the below FetchXML. It is supposed to add additional fields. 

count="1" >
   
       
       
       
           
           
       
   

The GUID of the resolved entity record is replaced with {[GIUDPLACEHOLDER]}

 
Figure 6: CustomXML dialog

Please note: We highly recommend to test the configured FetchXML query. To do so, we recommend the use of FetchXML builder for XrmToolbox http://fxb.xrmtoolbox.com/

6) Click on the [OK]-button in order to proceed. 

7) Next, download and install the latest TI Client version. (to be found in our Download area.)

8) Once this is done, please restart the TelephoneIntegration Client and simulate a call from the appropriate contact. To do so, right-click on TI Client Symbol in the StartPane, then click on Setup and search for the Simulator-tab). 
A possible result could look like this:

Figure 7: Additional Fetch result

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

This article explains how to enable the Click2Dial-functionality of TelephoneIntegration (TI) for CRM 2013/2015/2016 and Dynamics 365 without using the CallNumber button in the ribbon. 

This feature allows you to start an outgoing call through hitting directly on a telephone number in the CRM form via the TI Client. CRM already has a builtin Click2Dial feature, but its use is limited only to Skype or Skype for Business (Lync) client. 

Instead of calling via the default Skype or Lync client, we can alter it so that the call is triggered over our TI Client/default communication plugin.

Figure 1: Extended Click2Dial functionality (example)

 

How to extend the Click2Dial functionality for TI?

1) To enable the functionality, open CRM > Settings > Customizations > Customize the System.

In the next window select Web Resources in the tree-view and click on the [New]-button. 

 
Figure 2: Web Resources Window in CRM

2) Use the next window to create a new web resource. The name does not really matter. Here, we use new_ PTMTIReplaceCallHandler. The important settings are the Type and the Script.

3) Next, download the below file, unzip it and upload the script. 

For Dynamics 365 take this: PTMTIReplaceCallHandlerDyn365.zip 

For older CRM versions take this:: PTMTIReplaceCallHandler.zip​

4) Once done so, click on the [Save]-button and afterward on the [Publish]-button.

Figure 3: Create new web resource

5) Next, open a CRM record for which you want to enable this feature. (here: Contact) Here, open the Form-Editor.

Figure 4: Open form-editor in the entity Contact 

6) Now click on the [Form Properties]-button. 

Figure 5: Open the Form Properties - dialog 

7) In the Form Properties-dialog, the before created web resource must be selected. Click on the upper [+Add]-button (in the Form Libraries - section) and a Look-up record-window will pop up.
After the web resource has been selected, click on the [Add]-button in the Look-up record-window.

Figure 6: Form Properties-dialog (background) and Look-up record-window

8) Back in the Form Properties-dialog, we must define the Start-function of the script. To do so, click on the lower [+Add]-button (in the Event Handlers-section). Now select the web resource and type in the function name (here PTM_TIStartReplaceCallHandler). Click on the [OK]-button. 

Figure 7: Handler Properties 

9) Finally, the Form Properties-dialog will look like this:

Figure 8: Customized Form Properties-dialog 

10) To complete the configuration, click on the [OK]-button. Then click on the [Save]-button and afterward on the [Publish]-button in the form editor. 

Figure 9: Save and Publish

After reloading Contact in CRM (press F5), the Click2ToDial-functionality will be enabled.

Please note: If you want to enable this feature on additional forms, you simply have to select the corresponding web resource and define the corresponding start-function.

Trouble Shooting 
This section is only relevant for you if dialing out does not work as expected when clicking a number directly in the form.

First please make sure that dialing out by hitting the default TI button works as expected:

 

Only if this is the case it has to be a problem with the Click2Dial script.

Then follow these steps to get more information.

Add the "debug:true" text to the function call, as you can see in the figure below:

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

This blog article outlines how to create SharePoint locations, folders and subfolders automatically within MS Dynamics CRM with our DocumentsCorePack ServerBased Add-On.

The solution is our AutoMergeWorkingItem which can be triggered automatically when creating a new workflow in a process. 

Requriement: DocumentsCorePack ServerBased (DCP SB) Online

For further information how to do this in DCP OnPremise, please click here.

Example:

Standard SharePoint location in CRM:

Figure 1: Standard CRM SharePoint window

Created SharePoint location:

Figure 2: Created SharePoint location

How to manually save SharePoint locations, folder(s) and subfolder(s) in CRM when creating an account

Generally, when creating a new account in MS CRM, all appropriate documents (e.g. quotes, invoices etc.) are saved in the entity Documents in MS CRM.
As you can see in Figure 3, the CRM Save location Documents can be accessed via the drop-down-button next to the current company in the main navigation area at the top.
It could as well be accessed using our addon SmartBar, which enables a simple navigation between all related CRM records and entities. 

Figure 3: Save location of documents in MS Dynamics CRM

Anyway, to create a new Account in CRM, navigate to Accounts, then click on the [New]-button. 

 

Figure 4: Create a new account in MS CRM.

When you click on Documents (see Figure 3), the following message box appears. The box indicates, that a SharePoint location will be created manually with a click on the [OK]-button.

Figure 5: Message from webpage 

The standard SharePoint location-window is empty and does not contain any folder(s) or subfolder(s).

Figure 6: Entity Documents, once an account has been created.

Once documents have been saved, its look changes. 

Figure 7: Entity Documents with saved content

How to create a workflow that automatically generates SharePoint locations, folder(s) and subfolder(s) when creating an account

It is possible to create different subfolders in folders that contain certain documents (e.g. Quotes, Invoices …)

This can be managed with a simple workflow.

In our example we define

1) the SharePoint location,
2) the folder(s) and
3) the subfolder(s)
that will be automatically triggered when creating a new account. 

First of all, open your CRM and navigate to Settings and Processes.

Figure 8: CRM > Settings > Processes

Now create a new process with a click on the [New]-button.

Figure 9: Create a new process

In the next window, define the following settings:

- Process Name: (here: CreateSharePointFolder) 
- Activate As: Process
- Entity: (here: Account)     
- Category: Worfklow

Once this is done, click on the [Add Step]-button and select Create Record. 

Figure 10: Add a new step (Create record)

Now name the step (here: CreateFolder) and open the Drop-down menu within this first step: 

Figure 11: Name the new step

There, select MSCRM-ADDONS.com AutoMergeWorkingItems. 

Figure 12: AutoMergeWorkingItems

Next, click on the [Set Properties]-button.

Figure 13: Set properties for the new step

In the now following window, type in a name and define the AutoMergeWorkingItem-action (here, CreateSharePointFolder) It is also important to insert the PrimaryRecordUrl. To do so, set the cursor into the PrimaryRecordUrl-field and go to the Look for: -area within the form assistant on the right side. There, select Records URL(Dynamics) form the second drop-down menu. Click on the [Add]-button and on the [OK]-button in order to proceed. 

Figure 14: Create MSCRM-ADDONS.com AutoMergeWorkingItems

Next scroll down to the Create SharePoint Folder-section (see next screenshot, click to enlarge)

Figure 15: Create SharePointFolder-section

There, you can define the SharePoint location, folder(s) and subfolder(s). 

For example: TEST/subfolder 1;TEST/subfolder 2;TEST1/subfolder 1

Figure 16: Example SharePoint subfolder added


Figure 17: Structure of TEST/subfolder 1;TEST/subfolder 2;TEST1/subfolder 1

Figure 17 outlines, that a slash indicates that the subfolder remains in a mainfolder. Furthermore, it outlines that a semicolon indicates the creation of a new main folder.
Please note: the folder and/or subfolder name can contain blank space but you must not use a blank space between a folder and its subfoler(s) 

Once you have set up your order structure, please click on the [Save and Close]-button. 

Now click on the [Activate]-button in order to activate your workflow:

Figure 18: Activate workflow

Then click once again on the [Activate]-button in order to confirm the process:

Figure 19: Confirm the process

Now, your workflow is activated.

Figure 20: Activated workflow

Please note: it can take some minutes until the workflow has been entirely finished!

When you now create a new account and then navigate to the SharePoint document location, it should look similar to the example in Figure 21. 

Figure 21: Example - SharePoint document location based on workflow 

When opening the TEST-folder, the subfolders look as shown in Figure 22 and Figure 23.

Figure 22: Subfolder I

Figure 23: Subfolder II

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

This blog article outlines the DocumentsCorePack ServerBased send as pdf preview and edit functionality. The edit functionality allows to modify generated pdf-documents in MS Word before you send it to the customer with the DCP SB [Create document]-button. 

Please note, that the usage of SharePoint integration is mandatory in order to use the edit-functionality!

Requirements: DocumentsCorePack ServerBased (DCP SB) v.2015.18 for OnPremise, DocumentsCorePack ServerBased (DCP SB) v.2013.73 for the online version

Step-by-step description:

Generally, it is very easy to create and send e.g. quotes or an invoice to the customer with DCP SB. This can be done with a click on the [Create Document]-button inside the CRM CommandBar. 

Figure 1: Quote in CRM, ready to be sent via [Create Document]-button.

With a click on the [Create Document]-button the DCP dialog appears. Select a template from the list and click on the [Next]-button in order to proceed.

Figure 2: Template overview when processing a document via DCP SB

Now the DocumentsCorePack dialog appears.  

Figure 3: DocumentsCorePack dialog with its multiple functionalities.

Please note: the preview & edit function is only available for .pdf-files and the following Attach document-options:

- as note
- as email attachment
- as letter

Select your preferred settings and click on the [Next]-button within the so opened dialog in order to proceed. 

 
Figure 4: DCP dialog with different options.

In the next window, users have (next to option 3, that finishes every process), the following possibilities:

Figure 5: Options to modify the document

1 The Preview Document functionality

With a click on the linked quote 1 QUO-01001-8NTM05 (21) a new web client window opens allowing users to take a quick look at the document. There is no need to open MS Word. 
If the document is correct and no changes need to be done, close the preview window and finish the process with a click on the [Finish]-button (3).
 

Figure 6: Quote-document pdf.preview.

2 The [Edit]-button that enables you to edit your document
Please note: This option is only enabled if you have a SharePoint integration.  

If you wish to make some corrections, click on the [Edit]-button within the dialog. This will open the document in MS Word. There, all MS Word formatting-options are available.

Figure 7: Word document providing all MS Word formatting options.

Make your changes.  

Figure 8: Changes applied are marked in green

Once you have made your changes, close the document and save it with a click on the [Save]-button. Afterwards, you are redirected to the DocumentsCorePack dialog. There, click on the [Finish]-button in order to complete the process. 

Figure 9: Save changes 

A new CRM window opens that shows a new email with the attached pdf-quote. Scroll down to the Atachments-section to see the pdf.-document. 

Figure 10: Modified document as email attachment.

The document is now ready to go!

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

This blog article outlines how to configure CRM entities to show the DCP ServerBased [CreateDocument]-Button.

Requirement: DocumentsCorePack ServerBased CRM 2013/2015

1) Go to www.mscrm-addons.com and log in with your credentials 

Figure 1: www.mscrm-addons.com login

2) Next go to My Account and click on My cloud services 

Figure 2: My Account > My Cloud Services

3) Mark the service and click on the [Configure Service]-button

Figure 3: Configure the service

4) Here, you can configure on which entities the [CreateDocument]-button should be visible. To do so, click on the [Select Entities]-button.

Figure 4: Create Document Button Configuration
 

5) In the following window, select the appropriate entities by activating the checkbox and a click on the [Apply]-button. 

Figure 5: Apply configuration 

6) Now click on the [Save Service]-button and try it again!

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

This blog article explains what to do when you receive the following error message while saving documents to SharePoint.

DocumentsCorePack failed to generate the document

ERROR:|CHECKLICENSE|SUCCEEDED|new AutoMerge|StartMerge|ErrorMessage:No part of the path

Addon: DocumentsCorePack ServerBased (Online)

Please find here the OnPremise version of this blog-post.

Please note: The error usually occurrs because of missing or false SharePoint user credentials/rights.

It is mandatory that you have administrative access to SharePoint if you want to correct this error.

 

1) Go to www.mscrm-addons.com and log in with your credentials 

Figure 1: www.mscrm-addons.com login

​

2) Next go to My Account and click on My cloud services 

Figure 2: My Account > My Cloud Services 
 

3) The DocumentsCorePack Online Configuration appears. Please mark the service and click on the [Configure Service]-button.

Figure 3: Open the service configuration

4) Please check if username and password are correct, as well as if the user has administrative access to the configured SharePoint. 

Figure 4: Check your credentials 

5) If everything is alright, click on the [Save Service]-button and try it again!

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

This blog article outlines what to do if you receive the following error message while saving documents to SharePoint.

DocumentsCorePack failed to generate the document

ERROR:|CHECKLICENSE|SUCCEEDED|new AutoMerge|StartMerge|ErrorMessage:No part of the path

Addon: DocumentsCorePack ServerBased CRM 2013/2015 (OnPremise)
Please find here the Online version of this blog-post.

Please note: The error usually occurs because of missing or false SharePoint user credentials/rights.

It is mandatory that you have administrative access to SharePoint if you want to correct this error.​

Minimum permission of SharePoint user: 
Able to logon to the root site of SharePoint
Read access on the site
Read and write on the document library and all subfolders (create folders and upload files) 

For impersonation and SharePoint attributes: Site admin rights

​

1) Open your Dynamics 365 and navigate to Settings 

Figure 1: Dynamics 365 - Settings

 

2) In the Settings, click on Solutions

Figure 2: Solutions

 

3) There, double-click the DocumetsCorePackServerCore Solution.

Figure 3: DocumetsCorePackServerCore Solution

 

4) Please enter the credentials for your SPS user, the SPS password and the SPS domain.

Figure 4: Enter the credentials for the SPS user, password and domain

 

5) Now click on the [Save]-button and try again.

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

This blog article explains what to do if your desktop TelephoneIntegration (TI) Client is not working.

Please check your current Skype desktop Client version and make sure that is not higher than version 6.21.

The Skype desktop API commands for calls are broken in both 6.22 and 7.0. Skype developers are working to fix the problem. In the meantime, please use Skype version 6.21.

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