This is a known issue with versions previous to 5.28.

Please upgrade to at least this version : http://62.99.232.162/ti2011/tic530.zip to fix the problem.

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

The current version of RecordCounter for MS CRM 2011 contains performance updates. These updates will take effect, once the following changes have been made to the config.

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.

Basically, the default [Print in Word]-button contains JavaScript code in the background.

If you are familiar with CRM and JavaScript you can add your own custom buttons to  increase the usability of your CRM system.

e.g., you can predefine a template that should be always used to perform the merge. 

You can modify the JavaScript code, so that - based on certain criteria - a template is automatically selected without user interaction.

The following article contains a description of how to change, modify and extend this feature.

If you hit the [OK]-button on the RecordCounter Server Config first, it will generate and save the fetches and then generate and import the RecordCounterServerConfig-solution.

In some cases it will be helpful to only save the fetches or only to import the solution.

This article describes how this can be achieved.

On some occasions, unmanaged customizations to forms might prevent the setup to correctly configure the navbar section of entities.

You would see an error similar to this one, telling about a transition of an unmanaged solution being impossible. 

Figure 1: Error message (unmanaged solution)

+++++++++++++++++++++++++++++++++++++++++++++++++++
Please note 

This article only applies to the RecordCounter in Microssoft Dynamics CRM 2011. 

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

This article outlines what you can do if the AutoMerge Configuration page doesn’t load.

If the AutoMerge solution won’t load, please follow the below instructions.

This article describes the two different ways how the TAPI Test Tool can be started. 

If the calling/called phone number is stored in Microsoft Dynamics CRM, then the number should be resolved to the corresponded CRM record. If the number does not resolve, make sure that the number is stored in the "MSCRM-ADDONS.com CTI CallInfos" entity.