This article describes how to solve the description field problem in DocumentsCorePack. If you try to create an activity and it fails with the soap Exception you see below, it is due to the limitation of lenght of the “CRM description-field”. 

When using our products, the CRM discovery service is contacted to retrieve the service URLs for accessing the CRM WebServices.

In some cases the URL returned by the discovery service is not useable to contact the CRM WebService. 

Please note: This article applies to 

DocumentsCorePack ServerBased Document Generation & Processing
for Microsoft CRM 2013, 2015 and Microsoft CRM 2015/2016

ON PREMISE AND IFD ONLY 

(Click here for information on debugging in DocumentsCorePack Online) 

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

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

Please note: 
This article applies to
DocumentsCorePack CLIENT for MS Dynamics CRM 2013, 2015,
as well as for MS Dynamics CRM 2015/2016

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

When you search for big amounts of entities, a SQL TimeOut exception can occour. To minimize the amount of data, you can specify additional filtering in the PowerSearch Configuration (This filter must be manually inserted into the XML of the PowerSearch Config).

What to do if Chrome External Protocol Message does not pop up

If the [DocumentsCorePack]- and/or the [TelephoneIntegration (Call)]- button do not work with Chrome, you may have skipped an important message.

Issue:

AttachmentExtractor fails to upload files exeeding two megabytes of size (The actual size being blockes depends on various parameters and might actually be lower than the set value).

When phone numbers are not being resolved correctly, the cause is sometimes an incomplete phone number index table (to be found in the MSCRM-ADDONS.com CTI CallInfos) in CRM. 

It is recommended to rebuild this table from scratch. This includes removing all existing data in that table. To do so, we use the Telephone Integration update service. This article outlines how to do so. 

1. Open the IIS on the SharePoint server and navigate to the SharePoint Site where DocumentsCorePack (DCP) is configured and the UploadFile.asmx WebService is installed. Select the IIS Website and click on Explore as marked in Figure 1.