On a migrated organization, make sure the dcp/gc/ti security role migrated from CRM 4 is deleted.

This migrated role might interfere with the new setup and block the user from installing, because rights are checked wrongly.

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

To successfully integrate our products with custom entities, these custom entites either have to be part of a managed solution or the navigation configuration has to be applied manually.

• How to apply the changes manually 

To add the navigation links to the product, you will need to customize your entity form and apply the navigation links.

To do so, open CRM, navigate to the settings in the Navigation area and select Customization.

Figure 1: Select customization

Select Customize system and find the entity you want to edit in the new window.

This example is for entity Account.

Figure 2: Account > Forms

DoubleClick on the main form in order to open the form editor for this entity.

Click on the [Navigation]-button in the ribbon. The navigation area will become editable.

Figure 3: Click on the [Navigation]-button

Go to the Insert-tab and click on the [Navigation link]-button in order to bring up the new Navigation link form.

Figure 4: Insert-tab with [Navigation Link]-button

Figure 5: Navigation Link Properties

Link names and values for products

(Please note: Only insert links for products you have installed or you are currently installing, adding the link will NOT install the product)

Select the ptm_Icon16x16 as icon and switch the radiobutton to External URL.

As an URL specify the URL as defined in the Link item in the above list.

Figure 6: Insert icon and specify external URL

Now click on the [OK]-button, Save and publish the customization.

The link will now be available in your CRM

Please note: When you decide to uninstall the product, those links have to be removed manually as well. They do not harm the CRM, but will redirect to dead links, if you leave them in place.

• How to convert unmanaged custom entities to managed custom entities

Please note: This step can not be reverted without loosing data. Read carefully before continuing!

To enable the products to automatically configure your custom entities, these entities have to be converted into part of a managed solution.

This new managed solution will then be present in your CRM in the solutions list.

WARNING: If you choose to remove this managed solution you will LOOSE ALL DATA stored with the custom entities.

Do NOT DELETE this new solution, unless you are absolutely sure you want to remove the entities and all data stored with them.

The only way to restore the lost data is to restore the last SQL Server backup, loosing all other changes to data and schema applied after the last backup.

To convert your unmanaged entities to managed you need to create a new solution:

Select the [New]" href="http://mscrm-addons.com/images/blog/files/image_71.png">

Figure 7: All solutions

Select the [New]-button on the grid

Figure 8: Create a new solution

Create a new solution with your organizations default Publisher. Click on the [Save]-button.

Figure 9: Add entity

Add the entity (or entities) you want to convert.

Have a look at the webresources that might be needed by your custom entity. 

Please note: Only icons, onLoad/onSave event libraries, other resources include them in the solution.

Figure 10: Have a look at the webresources

Once you have added all entities, save the solution and export it via the export solution button in the menu.

Make sure all changes are published. The first dialog of the export wizard has a button to publish all customizations.

Figure 11: Export System Settings (Advanced)

You do not need to check any additional systemsettings in the above dialog. Simply click on the [Next]-button.

Figure 12: Export Solution - Package type

Please note: Make sure the solution is exported as managed.
IF you have accidently exported the solution as unmanaged, just repeat the process and make sure it is managed.

Save the exported file. You will need it soon again.

A managed solution cannot be imported over an existing unmanaged solution for the same entities.

Therefore, we have to delete the unmanaged solution we have just created to allow the import of the managed solution containing the same entities.

Deleting the UNMANAGED solution has no impact on the changes.

However, a deleted MANAGED solution will result in all data and schema being lost, that was defined in the managed solution.

Figure 13: Managed vs unmanaged solutions

It might take a few minutes to delete the solution.

Please note: Your customization is still present, even after deleteing the unmanaged solution.

Now we reimport the solution.

This will make all the changes part of the managed solution package.

Make sure this is the managed solution. Managed solutions usually carry the _managed suffix to the filename.

The system will inform you that some unmanaged adaptions will be migrated to the managed solution.

Figure 14: System information on solution 

The import might take a few minutes. Once it is done, you will be presented with a summary. 

Figure 15: Summary overview

Your entities are now part of a managed solution. 

Figure 16: Result - All solutions managed

Please note: From this point on REMOVING THE SOLUTION WILL RESULT IN UNRCOVERABLE DATA LOSS!!

Our products will now be able to automatically configure the entites.

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

Location of the Language Settings on the Client & Server

The name of the Language XML File is: .XML

For a list of two letter iso codes see http://www.worldatlas.com/aatlas/ctycodes.htm, Column A2

The language files are usually located in the sub folder localization of the products installation folder, typically under

C:\Program Files\PTM EDV Systeme GmbH\[ProductName] for MS CRM 4.0\Localization

or in the subfolder App_Data, similar to  

C:\Program Files\PTM EDV Systeme GmbH\[ProductName] for MS CRM 4.0\App_Data\Localization

The language file for the english UI is for example en.xml

CLIENT ONLY: Each client can have its own language files.

1.5.1.2 Modifying the UI language

The user language is retrieved from CRMs UserSettings and compared to the available language files .

If a matching language file is found, the contents will be used to localize the application.

If no language file is found, the default language as defined during the setup is applied.

To change the default language change the registry setting Language.

To modify this setting, follow this procedure:

1. Press START – RUN

2. Type regedit and click on the [OK]-button

3. Locate the registry key

3a. CLIENT: HKEY_LOCAL_MACHINE\Software\PTM EDV-Systeme\[ProductName]client

3b. SERVER: HKEY_LOCAL_MACHINE\Software\PTM EDV-Systeme\[ProductName]server

4. Change the value of the language setting to another language

5. Close the registry editor

If the default language cannot be identified, the system switches to english.

In order to create another language file than the provided language files, you need to create a copy of the en.Xml language file and rename it to the desired two letter ISO language code setting.

For example, to create a Dutch language file, copy en.xml, rename the copied file to nl.xml and then translate the strings in the file.

Afterwards, restart the client or close all your Internet Explorer windows and the new language will be applied automatically (as defined in your CRM user settings).

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

Outlook 2010 is having some severe problems with Ajax based functions. Being a reported error with Microsoft, there is still no fix available, but a workaround.

The impacted product cannot be started inside Outlook, but needs to be launched as a separate IE window.

You need to copy the ostarter.html into the root folder of the products server-side installation and adapt the sitemap as following:

Example GroupCalendar:

Per default, the sitemap is not having separate entries for WebClient and Outlook-Client, so you need to replace the existing SubArea (ID: nav_GroupCalendar) with these two new entries:

 
   

CTI does need the server component in a hosted environment as well, but you can launch the CTI Server setup from any Client, as long as you have a user with full access to CRM.

You need to select the hosted options on the Connection dialog. 

If you have physical access to the CRM server, you can simply launch the setup on that server as if it were an onPremise installation.

Due to the mechanics of an IFD setup, the client will not use a SQL connection to retrieve the information, but a webservice call.

As webservice calls are more limited as SQL queries, it is recommended to create a hidden field in CRM on the entities you want to search in.

They will hold the numbers in a format similar to the one TAPI uses.

You can achieve this either via an onSave script or via a workflow in CRM, transmuting the number to a TAPI compatible format.

This is only required for caller identification, outbound calls will work with the formatted number, because they are processed by the Client application.

Explanation:

The number stored in CRM is formatted canonical, looking like +43 (316) 680880 0

The TAPI drivers delivers a number as 00433166808800.

Though the information is the same, the formatting prevents the CTI to find the number, as the webservice call is not able to resolve the formatting.

If you have a field in the CRM entity that is getting filled with the unformatted number, you can setup the CTI to use that field for the lookup and get correct results in looking up the callers, but still have a well formatted number in the CRM to display.

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

Basics:
License-checks are done each time the application is accessed by a user.

Having an invalid license stops the whole product from working.

An invalid license will never have any impact on Dynamics 365, it only limits the addon itself.

Reasons for an invalid license :

• Wrong license OrganizationUnit
• Usercount has exceeded the granted licenses (Stops whole product, not only for the excessive users on all license models)
• Upgrading the product after having the support contract expired
• In case of a time limited license (and a trial): Reached the end of the license lifetime.

​

Licensetype normal license (aka perSite license)
Requires a license for each active Dynamics 365 user, no matter if he uses the product or not. If new Dynamics 365 users are added, the license needs to be extended with more users as well.

Disabled, ReadOnly users and Administrative users do not require a license.

Users without any security role can be exempted. Find more information about how to count only users with security roles for licensing here.

Service app security roles are excludet. 

Licensetype perUser license
Requires only as many licenses as you actually want to have, but starts at a minimum of 10 licenses and is double the price of a site license.

The license is a named user license and the license is activated via a checkbox on the Systemuser entity for a specific user.

You may activate as many users for the access as you have licenses.

Exceeding the granted license count stops the product for all users.

​

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

Trendmicro Officescan (Version 10, Servicepack 1).

Lösung: Mit dem Trendmicro Performance tuning Tool (siehe Link) eine Ausnahme auf die CallInfoCRM4.exe erstellen.

Die Ausnahme wird, obwohl im TM Artikel nicht erwähnt, in die globale Konfiguration aufgenommen. LINK

Das war's auch schon! Wir freuen uns auf Ihre Rückmeldung! Schicken Sie diese bitte gerne per eMail an support@mscrm-addons.com.