Connector -- Integrating Dynamics ERP with Dynamics CRM

Connector for Microsoft Dynamics is an integration solution which is targeted specifically at the Microsoft Dynamics product family. Connector provides an out of the box integration between Dynamics CRM and Dynamics ERP solutions.

Connector for Microsoft Dynamics V2 RU3 released today

Connector for Microsoft Dynamics V2 RU3 released today

Rate This
  • Comments 23

Connector for Microsoft Dynamics V2 RU3 (2.3.1306.1) released today!  This release enables integration with Microsoft Dynamics AX 2012 R2, and also resolves some of the key issues that you might be facing with your RU 2 deployments.  Additional features and updates are listed later in this post.

Note: that if you are using Microsoft Dynamics Online or are planning on up-grading your on-premises deployment to the upcoming UR 12 update for Microsoft Dynamics CRM 2011, you will need to continue to use the classic forms for the Account, Contact, and Sales Order entities and ensure that the Connector for Microsoft Dynamics solution you have loaded in Microsoft Dynamics CRM 2011 is at least version 1.0.1603.3.

To download this release for your Microsoft Dynamics ERP system, go to Customer Source:

Would you like to know more?  Check out the User Guide for your ERP system and begin your installation preparation. I know, I know; reading documentation can be an arduous task. But you know what they say: an ounce of prevention is worth a pound of cure. So read the provided documentation to avoid the common mistakes and save yourself the support call.

Here is an overview of the feature list:

  • Features across ERPs
    • Entity References in Microsoft Dynamics CRM 2011 are no longer fully validated, meaning that is you have been getting error related to an instance of an entity “not having a value for its dynamics_integrationkey” attribute then you should no longer see these errors after upgrading
    • The Microsoft Dynamics CRM configuration utilities now list all of the entities available by default rather than having to expand the list
    • Filtering now supports converting from a nullable type to its base type, so you can base a filter on a nullable Boolean and compare it to a standard Boolean without having to add extra functions to the filter
    • Custom entities in Microsoft Dynamics CRM that have the same display name as the standard entities are now supported
    • Custom entities and their attributes are now in the administrator’s language when running the configuration utility for Microsoft Dynamics CRM and when viewing the map
  • Features for Microsoft Dynamics AX
    • Microsoft Dynamics AX 2012 R2 is now supported
    • Microsoft Dynamics AX 2012 adapter now supports converting its DAXIntegration keys from attributes that are of a .NET primitive type rather than just from a GUID
    • “Socket Connection was aborted” errors when integrating into AX 2012 are now handled properly
Please only post comments relating to the topic of this page.
If you wish to ask a technical question, please use the link in the Related Links section (scroll up, on right hand side) to ask on the Dynamics Communities. If you ask on the Communities, others in the community can respond and the answers are available for everyone in the future.
Leave a Comment
  • Please add 1 and 1 and type the answer here:
  • Post
  • Great, keep up the good work :)

    I'm glad that we are getting rid of the entity reference errors when we have related entities :)

    We though still need the possibility to avoid deletes and have different maps for updates and inserts which would be really great to have in a future release.

  • @Jack DS - as always, Jack, thank you for your feedback and continued use of Connector for Microsoft Dynamics!

  • Great to see that the connector is being updated frequently.

    Is an undate required to have the Connector function with the 'Polaris' CRM update?


  • @Thomas - any version of Connector that includes the 1.0.1603.3 version of our Microsoft Dynamics CRM 2011 solution will work with the "Polaris" or UR 12 version of Microsoft Dynamics CRM 2011 to our knowledge.  The only caveat is that you must use the "classic" forms for the account, contact, and sales order entities since the solution adds a submit button to the ribbon on those forms.  This version of our solution has been included with the Connector releases since the RU 1 release.  The version history can be found here:

  • This is good stuff. Like a lot of people, I'm glad the connector is being updated frequently. Kudos to the team!

  • Hi Chris and Connector Team/Community,

    We are using the latest Connector for MSD V2 RU3 (support for AX 2012R2) to integrate AX 2012 R2 and CRM 2011 On-Premise.

    We have successfully configured both the AX 2012 and CRM 2011 Adapters and we are now attempting to activate the maps for initial data synchronization, but having errors with the first map: Enumerated Values to Picklist.

    We are running for the 1st time the [Enumerated Values to Picklist] map and we are getting some errors.

    Here's the complete error log:

    [Enumerated Values to Picklist] has encountered an error while processing key [Customer]. ERROR: Unable to add CoOp  Exception:   SecLib::CheckPrivilege failed. User: ad71241c-e416-e211-8963-0050569c015d, PrivilegeName: prvWriteAttribute, PrivilegeId: 6fa055d5-e524-4eed-a48e-8af713f83ff4, Required Depth: Basic, BusinessUnitId: 43914ff6-0213-e211-ae12-0050569c015d

    Our initial investigation is that its a User privilege issue, but we've verified that both the Installation Account and Integration Account have the necessary Security Role and Access in both AX and CRM.

    If anyone has experience with the error or if you have any idea on how to resolve this error, we would appreciate your assistance.



  • @Progressive - this is definitely a user permission issue within CRM.  I would suggest contacting support to work through this issue.

  • Thanks Chris! Another clarification:

    We are currently using CRM 2011 On-Premise with Update Roll up 11. Do we need to install the latest UR 12 to be able to integrate successfully with AX 2012 R2 using the Connector V2 RU3?

    I saw on the latest guide "MSDynConnectorAXconfig.pdf" released Jan. 2013, that a connection with Microsoft Dynamics CRM 2011 on-premises with the most recent rollup applied is a requirement, but I just want to verify this with you and your team because of the late/delayed release of UR 12 for On Premise.



  • @ProgCRMKen - UR12 is NOT required for Connector RU3.

  • What about the update of Contact info from CRM to AX, specifically for contact details (such as telephone, fax, mail, …)?Seems not to work ... Any ideas ?

  • @Christian - the updates for contact info items in AX 2012 from CRM are currently not supported as pointed out in the AX user guide for Connector.  This is due to a limitation in AX that we are currently working with that team on.  Unfortunately I do not have an update as to when this might be supported but we are working on it with the AX team.

  • Hi theHetz, thanks for the quick update :). Any idea about the timing for a possible solution ? This rather blocking for our customer :(.

  • @Christian - Unfortunately no, we don't have a timeframe from that team, if you have any contacts in the AX organization I would suggest mentioning this issue to them as well to help with our traction on the issue.

  • Hi theHetz, thanks for the quick updates ... will escalate

  • Does Connector for Microsoft Dynamics (Dynamics AX ) required license or registration key?

Page 1 of 2 (23 items) 12