Print

The latest release information about the Dynamics CRM Campaign Integration.

1.  Release History

Some of the issues described on this page contain internal reference numbers. You can use these reference numbers when communicating with Sitecore about a particular issue or feature.

September 20, 2012

The CRM Security Provider module 1.1.0 rev. 120822 is released.
Tested with Sitecore CMS 6.5 Update-5.

Compatibility
This version of the module runs on Sitecore 6.5 and later.

Change log.

Improvements:
A number of improvements have been made which have significantly increased performance.

• CRMProviderProfiler.html  page was added to the package and is available in sitecore/admin/ CRMProviderProfiler.html . It contains performance counters for Membership, Role and Profile providers (370750)
• The number of calls required to retrieve CRM contacts has been reduced as well the cache required for each user (366633, 360429)
• Cache for Users and Roles has been separated. Now we have cache size and lifetime settings for Roles in the config (368761)
• The time required to retrieve a large amount of CRM contacts in particular role has been reduced (366632)
• Contacts are retrieved from CRM with all required attributes/fields in order to improve performance (368509)
• Microsoft Dynamics CRM returned maximum 5000 entities that shown as members of the particular role in Role Manager. This limitation has been removed (360497)

Issues resolved:

• An issue causing User Manager and Role Manager to fail when the Dynamics CRM server is unavailable or there are incorrect connection credentials to it has been fixed (349566, 359319)
• An issue causing issues with password storage when using a non-English Online has been fixed (366966)
• An issue which caused the creation of Target Audiences for Email Campaign Manager in cases where the "Common Domain" field value was set to "crm" has been fixed (360815)
• An issue causing the roles cache in the Roles Manager not to expire certain configuration settings has been fixed (362443)
• An issue which caused the Role Manager to hang while retrieving more than 50000 members of a particular role has been fixed (363134) 

December 30, 2011

The CRM Security Provider module 1.1.0 rev. 111226 is released. Valid for Sitecore CMS 6.X. Tested with Sitecore 6.5.0 rev. 111123.

Change log.

Improvements

• Caching of all retrieved user profile properties has been added. When CRM Provider reads any user profile property from CRM, it retrieves and caches all available properties avoiding additional requests to CRM. (356406)
• The Crm.Profile.Prefetch setting has been added to the CRM Security Provider configuration file. It determines the list of properties that are loaded together with any CRM contact and allows access to all required properties removing the need to perform another call to CRM. (356404)

Issues Resolved

• An issue causing CRM security provider to fail at initialization in some cases due to a dependency on specific assembly versions has been fixed. (350278)
• An issue causing CRM security provider not to connect to CRM online when Application Pool identity is NETWORK SERVICE has been fixed. It was due to standard limitations of Microsoft Identity Client Run Time Library. (351271)
• An issue which caused caching to work incorrectly in non-UTC time zones if the cache lifetime is less than 8 hours has been fixed. (356373)
• An issue which caused cache to be created too often has been fixed. (355447)

August 02, 2011

The CRM Security Provider module 1.1.0 rev.110622 is released. Valid for Sitecore CMS 6.X. Tested with Sitecore CMS 6.5.0 rev. 110602.

Change log.

Added Environment Support

• Support for Microsoft Dynamics CRM Online systems in the Password authentication mode has been added for 64 bit systems. (332315)
• Support for Claim Based Authentication in Dynamics CRM 2011 has been added. (345929)

Issues Fixed

• An issue causing CRM Security Provider not to work when domain name is specified in the “user id” parameter of connection string. (349817)
• An issue causing problems when using the module with CRM Online 2011 in Europe and Asia has been solved. (347936)
• An issue causing Sitecore to fail to start when the Dynamics CRM Security provider is installed and the Dynamics CRM server is unavailable has been fixed. (332620, 345466)
• A caching issue, which cause some users in a role not be correctly cached has been fixed. (345896)
• An issue occurring when using the module with CRM v. 4 web services and  IFD authentication and causing the module to stop working when the authentication ticket expires has been fixed(346603)
• An issue with adding and removing users from roles occurring when using the module with CRM v 3, and 4 has been fixed. (347556)
• An issue causing checkbox fields  in the User Profile not to function correctly has been fixed. (337942)

Improvements

• Roles are now cached in the Dynamics CRM Security Provider in order to improve performance. (344929)
• The log information provided by the module has been extended to include the data extracted from the CRM, including previous values of fields.(337945)

June 8, 2011

Dynamics CRM Save Actions 1.0.0 rev.110303 were tested with Sitecore CMS 6.5 rev. 110602.
Dynamics CRM Security Provider 1.1.0 rev.100624 was tested with Sitecore CMS 6.5 rev. 110602.

March 29, 2011

Dynamics CRM Campaign Integration has been tested and verified with Microsoft Dynamics CRM 2011. Both Online and On-premise versions of Dynamics CRM 2011 are supported.

March 18, 2011

Dynamics CRM Save Actions 1.0 rev.110303 is released.

This release is only compatible with Sitecore CMS 6.4.

July 1, 2010

The Microsoft Dynamics CRM Campaign Integration is released.

Tested with Sitecore CMS 6.2.0 rev.100507 (Update 2).

The Microsoft Dynamics CRM Campaign Integration consists of the Dynamics CRM Security Provider 1.1 and the CRM Dynamics Save Actions for the Web Forms for Marketers module.

Dynamics CRM Save Actions 1.0.

The Dynamics CRM Save Actions require a Microsoft® Dynamics CRM Campaign Integration license.
For more information about the features of the CRM Save Actions see the Dynamics CRM Campaign Integration What Is new document and the Dynamics CRM Save Actions User Guide in the Documentation section.

Dynamics CRM Security Provider 1.1.

New Features:

• The module now supports Microsoft Dynamics CRM v 4.0. CRM 4.0 contains significant performance improvements, particularly in the web services used by Sitecore’s Dynamics CRM Security Provider. It also facilitates modifying metadata via the CRM web services. (327162)
  The module is still backwards compatible with version 3 of Dynamics CRM.
• The module has been tested, verified and optimized for use with CRM Online.
• Caching  has been optimized. This and other improvements have improved performance of the module by up to 450%. (327164)
• Additional  debugging functionality has been added and can be utilized in the CRM providers (327168)
• Users are now able to utilize all the connection properties that CRM provides in the module to optimize the connection to their CRM configuration.  (327173)

 Important changes:

• Dynamics CRM Security Provider 1.1 requires a Microsoft® Dynamics CRM Campaign Integration license.

Issues resolved:

• It is now possible to automatically add a password field to the contacts entity in CRM (310076)
• Inactive contacts were returned as marketing list members. These are now ignored. (325204)
• The value of the URL parameter in a CRM connection string is now case-insensitive. (326755)

2.  Known issues

The following known issues have been found in the Dynamics CRM Campaign Integration.

1. Dynamics CRM Campaign Integration doesn't support authentication through Microsoft Office 365.
   Reference number: 372449, 385682
   Description: It's impossible to connect Microsoft CRM Online via the Dynamics CRM Campaign Integration module using the Microsoft Office 365 authentication. Dynamics CRM Campaign Integration only supports Passport authentication in its current implementation. The Microsoft Office 365 authentication type is current the primary authentication type. It is also used as the default authentication type for newly created organizations.
   Solution: You can register a new CRM organization using the existing Windows Live ID account:
   1. Log in to the Microsoft CRM portal using the existing LiveID. You will receive the following message:
       "You have signed in with a Microsoft account that is not part of an organization. You can try signing in with another Microsoft account that is a member of an organization"
   2. Press Cancel.
   3. Click "Sign up for a new Microsoft Dynamics CRM Online account" and perform all the necessary steps.
   Note: This known issue was fixed in the Dynamics CRM Campaign Integration 2.0.0 rev.130731.
2. User Manager fails if one of the CRM users contains commas in the name.
   Description: User Manager fails if one of the CRM users contains commas in the name.And it’s only in case if the default “Crm.UniqueKeyProperty” setting was changed in the config file. This is due to a CMS issue, which will be fixed in a upcoming CMS update.
   Reference number: 341955.
3. Dynamics CRM Campaign Integration doesn't currently support WCF services.
   Applies to:  Dynamics CRM Security Provider 1.1.0 rev. 111226 and earlier / Dynamics CRM Save Actions 1.0.0 rev.110303 and earlier.
   Reference number: 353476
   Description: Dynamics CRM Campaign Integration doesn't currently support WCF services. The connection strings in the following format shouldn't be used:
   http://test.api.crm5.dynamics.com/XrmServices/2011/OrganizationData.svc
   Solution: Please use the following format instead:
   http://test.api.crm5.dynamics.com/mscrmservices/2007/crmservice.asmx
   Please refer to the following documentation for more information about the CRM connection string format:
   http://sdn.sitecore.net/Products/Dynamics%20CRM%20Campaign%20Integration/DCRMCI1/Installation.html
   Note: This known issue was fixed in the Dynamics CRM Campaign Integration 2.0.0 rev.130731.
4. The Role Manager fails if the CRM Security Provider is turned off.
   Reference Number: 349566.
   Note: This known issue was fixed in the Dynamics CRM Campaign Integration 1.1.0 rev. 120822.