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.

More...

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 

The first step to solve this issue is to identify the causing entity.

You need to find the purple highlighted errortext in the XML tree.

Follow the tree up till you find the formXML node. The localized name will tell you which entity is failing. You need to uncheck this entity from all locations in the configuration. You can process all other entities as normal.

Adding the NavBar entry manually :

You need to be administrator to be able to complete the following steps :

Open up any record of the entity you want to customize (Account for this example)

and open the form designer

Enable the navbar editing

and insert a new item

On the following dialog enter a name (Like EmailPreview or ActivityPreview), select the ptm_Icon16x16 webresource for the icon

Select the ptm_webApplicationPreloaderActivityPreview to add the ActivityPreview functionality or select the  ptm_webApplicationPreloaderEmailPreview to add the EmailPreview.

If you want to enable both, you need to repeat the same steps for each item. 

Close all forms, and do not forget to save&publish the changes or the changes will not show.

This article describes how you can activate debugging for RecordCounter for CRM 2011. It also shows how you can access the log files.

More...

This article describes how you can solve the problem that the AutoMerge Configuration page doesn’t load.

If the AutoMerge solution won’t load like in the screenshot below, please follow the instructions of this article.

More...

This article describes how to activate debugging for AutoMerge for CRM 2011.

Basically there are two possibilities to enable debugging.

Solution 1: Activating debugging by using the AutoMerge Configuration (Recommended way, only if the AutoMerge Configuration doesn’t work use the second solution). 

Solution 2: Activating debugging manually via MSCRM-ADDONS.com Settingskeys.

More...

You can start TAPI Test Tool by two ways:

• go to installation path where your TI client is installed and start PTM.TI.TAPI2CallOut.exe 

• download TAPI Test tool from www.mscrm-addons.com and run PTM.TI.TAPI2CallOut.exe

After start you must choose your TAPI line and press "Next". If your TAPI line is not seen, then check that your TAPI driver is properly installed.  

Now you must make an incoming call to your TAPI line. At best you try with an external number (from your cell phone). 

After accepting the incoming call by your TAPI phone device, end the call, press "Next" and make one outgoing call back to your cell phone. Accept the call by your phone call if ringing.

After accepting the outgoing call by your cell phone, end the call, go "Next" and Email the content of your TAPI testing to support@mscrm-addons.com.

Normally, there should be logging information by incoming and outgoing calls. If not, then you must check with your TAPI administrator that you have no lack in access/monitor rights to your TAPI line.

If the calling/called phone number is stored in CRM, then the number should be resolved to the corresponded CRM record. If the number does not resolve, then check if the number is stored in the "MSCRM-ADDONS.com CTI CallInfos" entity. For that go into Advanced Find  

where we searched the number 31668088036. By pressing Results button we must get at least one found record. In the phonenumber collumn we see the full canonical format of the number with country code.

If we did not find the number in advanced Find, then check your fields.xml setting if the number is stored in the choosen entity / searchfields.
For example ... if the number is stored in Contact entity under mobilephone field, then mobilephone field must be in fields.xml setting under <contact><searchfields>telephone1,telephone2,mobilephone,...</searchfields>

Delete the phone number in Mobile Phone field (for now we assume, that mobilephone field is in <searchfields> content and then store the number again under Mobile Phone field. Go back in Advanced Find and check the phonenumber in MSCRM-ADDONS.com CTI CallInfos entity. The number should now be stored in that entity in its full canonized form. If not, then something can be wrong with CRM Asynchronous services. Check if those services are running.

If AdvancedFind return at least one record, matching our number, then something is wrong with TI client. Check that the calling party phone number is not an internal number. If it is not, activate debugging and make one incoming or outgoing calll with that number and send us the generated log file.

Remember that shorter the log file, sonner can developer find the essential data to solve the problem. 

A new feature of GroupCalendar version 4.84 is a print preview of the Gantt View. This requires a small client side installation.

When you click on "Print Preview" in GroupCalendar on the bottom right corner, you'll see a message that the ActiveX control is not installed. You'll find the ActiveX in the GroupCalendar installation directory on the CRM Server in the subfolder ActiveX e.g. C:\Program Files\PTM EDV-Systeme GmbH\GroupCalendar for MS CRM 4.0\ActiveX

You need to run this installer on the clients which want to use the print functionality.

If you want to uninstall the ActiveX, run the installer with the parameter /u. e.g. RegisterActiveX.exe /u

Please select the correct product and CRM version form the table below and follow the link to get redirected to a description of how to do this.

Starting with version 5.23 / TI and version 5.19 / DCP in combination with LicenseManager 5.2 the ribbonButtons will be disabled on perUser licensing, if the user is having the acccess flag for the product set to no.

Licensemanager 5.2 creates a new setting, "IsPerUserLicense" with value true|false when importing a licensekey.

Based on this setting being true and the Users access flag (perUserLicensing[Product]) the button will be disabled.

The funtionality is requiring general solution v46.0