Release Notes > Summer 2016 - June > Microsoft Dynamics CRM Connector
  

Microsoft Dynamics CRM Connector

After You Upgrade

After you upgrade the Microsoft Dynamics CRM Connector, perform the following steps:
    1. Move the US_export_policy.jar and local_policy.jar files, and cacerts files from <SecureAgent_InstallDirectory>\main\jre2\lib\security to <SecureAgent_InstallDirectory>\main\jre\lib\security.
    2. Move the login.conf and krb5.conf files from <SecureAgent_InstallDirectory>\main2/bin/rdtm/javalib/msdcrm/conf to <SecureAgent_InstallDirectory>\main/bin/rdtm/javalib/msdcrm/conf.
    3. If you use Microsoft Live or Internet Facing Deployment authentication type, specify the runtime environment for an existing connection before you use it.

Microsoft Dynamics CRM Connector Fixed Limitations

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
CR
Description
CON-3047
When you edit a Mapping Configuration task, there is a delay when you navigate from one tab to another.
CON-2618
When you use Microsoft Dynamics CRM Bulk API in a Data Synchronization or Cloud Mapping Designer task to insert a GUID that is not valid, the Secure Agent aborts the task.
CON-2029
When you run a Data Synchronization task or Mapping Configuration task that writes to a Microsoft Dynamics bulk API target, the agent does not write error rows to the error file.
CON-1934
If you connect to Microsoft Dynamics CRM live with ADFS, authentication fails with the following error:
Access is Denied
CON-1933
After you run a task, the task thread pool does not close.

Microsoft Dynamics CRM Connector Known Limitations

The following table describes known limitations:
CR
Description
CON-3144
When you configure a Data Synchronization task, data preview does not display PartyList data type fields.
CON-3049
If you filter source data by using the $LastRunTime variable in a Data Synchronization task or a Mapping Configuration task, the task fails with the following error:
ERROR arg1=Invalid XML. arg2=null arg3=null arg4=null arg5=null
CON-2617
Error files are created in the default location even when you specify a custom location in the Error Log File Directory field in a Cloud Mapping Designer task. All error files are created in the following directory: <Secure Agent Installation Directory>\main\rdtmDir\error.
CON-2610
If you download and open or view an error file, the error file does not display all the error rows.
CON-2386
If you filter source data by using the $LastRunTime variable in a Mapping Configuration task, the task fails to filter the data.