Connector for Microsoft Dynamics V3 CU 4 released


Support for Microsoft Dynamics CRM 2015 is the primary new feature in Connector for Microsoft Dynamics V3 CU4 (3.4.304.1) which was posted today, December 10th, 2014.

Important release information: 

This version of Connector NO LONGER supports integrations with CRM 2011 or CRM 4.0.  If you have existing integrations to CRM 2011 or CRM 4.0, DO NOT apply this update to those integrations or upgrade the integrated CRM organizations to CRM 2013 or CRM 2015 before applying this update.  Creating a new integration to CRM 2013 or CRM 2015? Then this is the version of Connector that you will want to use.  Creating a new integration to CRM 2011?  Then you will need to use the CU 3 version of Connector which is still available at the download sites listed below. If you have been upgraded to CRM 2015 and have an existing integration using Connector, see the upgrade section below.

Note: The support for creation of new integrations to CRM 4.0 was discontinued several releases ago.

New features with this release include:

  • Support for CRM 2015, which requires the updated CRM solutions included in this release (1.0.1603.5) - these CRM solutions include "CRM2015" in their file names
    • These solutions also provide support for both the summary and information forms for the targeted entities within CRM 2015
  • New mappings for Microsoft Dynamics AX and CRM Contact integration that handle the new address 3 fields included in CRM 2015 contacts properly.  Those changes can be found in the map changes section.
  • The required Microsoft .NET Framework versions (3.5 and 4.5.2) are checked for during installation.  The Microsoft .NET Framework version 4.5.2 can be downloaded here: web installer or offline installer.
  • The new integration template for creating and integration between Microsoft Dynamics GP and CRM using CRM contacts has been removed 
  • All previous updates for CU 3 have been incorporated into this release

Downloads:

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

  • Connector for Microsoft Dynamics AX
    • If you have applied AX 2012 R2 CU 6 or later or if you are targeting AX 2012 R3, an XPO is no longer needed.  You can run the ConnectorHelper class that is included in those releases to accomplish the required setup tasks in AX 2012 R2.
    • Any release after Connector V3 CU2 (3.2.606.2) will support AX 2012 R3
    • AX 2012 R3 CU 8 is fully supported
    • The contact integration maps have been updated to include mappings for the new CRM 2015 address 3 fields, see the map changes section for more information on these changes
  • Connector for Microsoft Dynamics GP
    • All previously supported versions of GP 2013 are supported
    • GP 2015 is fully supported
    • The ability to create an integration from a template using GP customers and CRM contacts has been removed
  • Connector for Microsoft Dynamics NAV
    • Microsoft Dynamics NAV 2015 and all previously supported versions of Dynamics NAV are supported with this release
    • If you are targeting a multi-tenant deployment of Microsoft Dynamics NAV 2013 R2 this release will make that configuration and integration process easier.  The steps outlined in this post are no longer need with this release of Connector for Microsoft Dynamics.
  • Connector for Microsoft Dynamics SL
    • Previously supported versions of SL continue to be supported by this version

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 arduous. 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.  The user guides for all of the ERPs have been updated for this release and all include a V3 upgrade sections that you should be familiar with before upgrading your existing integrations.  All of the known issues documents have been updated as well so please have a look at those too, they can all be found on the Connector download pages. 

Upgrade information:

If you have an existing integration between a Dynamics ERP and CRM and you have been upgraded to CRM 2015 please follow these steps to continue using Connector

  1. Deactivate all currently active maps in all integrations
  2. Stop the Connector for Microsoft Dynamics service
  3. Run the Connector V3 CU 4 MSI for your version of Connector to upgrade your installation of Connector
  4. Import the updated CRM solution into the integrated CRM 2015 organization for your targeted ERP integration
    1. In CRM 2015 navigate to Settings, Solutions
    2. Select to import a solution
    3. Select the updated Connector solution for your targeted Dynamics ERP.  For example in the case of an AX integration this would be C:\Program Files (x86)\Microsoft Dynamics\Microsoft Dynamics Adapter\CRM2015ConnectorForMicrosoftDynamicsAx.zip
  5. Start the Connector for Microsoft Dynamics service
  6. Run the CRM configuration utility for each upgraded CRM organization, selecting to "Skip complete configuration and only generate entity configurations".
    1. This will re-generate the configuration files for all of the entities that they were previously generated for.  If you have hand-edited these files for any reason you will need to re-apply those edits by hand.
    2. Caution: If you do not select the "Skip complete configuration and only generate entity configurations" option in the configuration utility the targeted CRM organization's entire product catalog will be deactivated, re-named, and will need to be re-integrated.
  7. Update your existing contact integration maps if you are integrating with AX
  8. Re-run the Enumerated values to Picklist map
    1. In order to do this operation you will need to set the "check for data modified after" and the "Start date" to 1/1/1900 and then activate the map and save your changes
    2. The above sub step is required because the Enumerated values map is set to be a run once map by default
  9. Re-activate any maps that were active before

AX Map changes

If you have not edited your integration's contact maps you can delete the existing maps and import the news using the "Create map from file" feature within Connector.  You will want to do this after upgrading you integrations as noted above.  If you have customized the contact mappings then you can use the following section to update your existing maps to compensate for the new Address 3 fields in CRM 2015.

  • Contact Persons Service to Contact map
    • Address 3 Integration Key
      • =GetSecondaryAddressId(Person, 2)
  • Contact to Contact persons Service
    • Person\Item\Postal Address View\Item\Roles
      • =If(EqualTo(All Addresses\Customer Address\Address Number, 1), If(IsDefaultValue(Address 1 Address Type\Name), "Other", Address 1 Address Type\Name), If(EqualTo(All Addresses\Customer Address\Address Number, 2), If(IsDefaultValue(Address 2 Address Type\Name), "Other", Address 2 Address Type\Name), If(IsDefaultValue(All Addresses\Customer Address\Address Type\Name), "Other", All Addresses\Customer Address\Address Type\Name)))
Comments (31)

  1. Arndt says:

    no new SDK available ? for example a new template for VS 2013 ?

  2. thehetz says:

    @Arnt – No the SDK has not been updated for this release.

  3. Hassan says:

    Hi;

    Thanks for sharing, I followed the steps, but when I create integration from template and save it I got this error (I found it on event viewer

    "Unhandled exception. This may indicate a problem with the application but may not be

    fatal. — Exception Dump ..

    any idea's ?

  4. thehetz says:

    @Hassan – this could be caused by many things.  Were you able to successfully test the connections to the end applications?  Have the configuration utilities been run for CRM and your ERP?  I would suggest logging a support case so our support engineers can guide you through the process of creating a new integration.

  5. Hassan says:

    After importing the solution in CRM 2015 , I noticed Hirarchy Visualization does not show no more

  6. Hassan says:

    just to clarify, this is on CRM 2015 and on sample company. after importing connector solution. no hierarchy shows for Accounts and contacts in CRM ( the solution only applies on contact and account)  while product have the hierarchy (product is not impacted with the solution)

  7. thehetz says:

    @Hassan – I would need more information to assist with this issue.  Have you entered a support request?  I am not aware of anything in the CRM 2015 solution that would cause this to happen directly as a result of the import.

  8. Hassan says:

    I did not list it as ticket yet, save them for more urgent issues 🙂

    for the case, in CRM 2015 they have hierarchy visualization as new feature on some entities such as account, contact and product. sadly After importing connector solution on CRM to complete Connector integration, hierarchy does not show on CRM- account and CRM-contact no more, while it is showing on CRM-product. when I checked the solution I imported it has updates on Account and Contact form not product. so I concluded it has to do with connector solution.. any suggestions?

  9. thehetz says:

    @Hassan – I'm not sure why our solution would have an effect on this functionality.  I would suggest contacting someone on the CRM team or perhaps posting the question in the CRM developer community.

  10. Black Theridion says:

    Hi,

    I have created a new adapter with the SDK, but the Dynamics Connector does not see the new Adapter. I have added the 3 sample adapters, they do not show up either.

    I have seen that the objects of the SDK are four years older than the connector objects. Is the given SDK in the Connector page up to date and compatible with the V3 CU4?

    Jerome Piquot (Flexmind)

  11. thehetz says:

    @Black – yes the SDK projects are still compatible with Connector for Microsoft Dynamics V3 CU 4.  You will need to fully strong name sign the adapters in order for them to be picked up by the Connector service and restart the service after they are deployed.

  12. Black Theridion says:

    Hi @thehetz,

    On your advice, i have signed the dll but the CRM connector still doesnt see the new adapters.

    But when i have changed the default rights on the adapters directory by adding the connector service run user to have full rights, the connector can now see the signed adapters.

    Thank you very much for your quick answer that put me on the solution.

    Jérôme Piquot

    Your help was very usefull.

  13. paolo titta says:

    CRM Connector is hanging only if I MAP a specific entities. Theese entities are migrated from CRM2011.

    that the stack:

    WARNING TID:TP-11 [2015-04-24T10:16:27.1682756+02:00]: There was no endpoint listening at http://localhost:4740/configuration that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

  14. thehetz says:

    @Paolo – Please verify that the entity does not have any self referencing attributes.  This is not supported by Connector and this update has logic in it to detect that in the mappings.

  15. Daniel Bergsten says:

    Hi! I have two questions:

    1) Is CRM 2015 product bundles supported with the Dynamics Connector for NAV?

    I've tried to set this up but I can't submit an order (CRM) as a business process exception happens:

    Required bundle item cannot be updated

    Microsoft.Dynamics.Integration.Adapters.Crm2011.Plugin.OrderNavCreateUpdateEventHandler (SetStateDynamicEntity of salesorder)

    2) Is it possible to use the CRM "override price" functionality for orders when using the Connector for NAV? Pricing: Use default/Override price.

    The users needs to set prices in CRM…

  16. thehetz says:

    @Daniel –

    1. This has not been tested and I am use if it will work or not.  It seems from your findings below that it does not in this case.  Is the bundle an item that was integrated from Dynamics NAV?

    2. I believe that it is possible to override the pricing on an item when originating an order in Dynamics CRM that is then submitted to Dynamics NAV.  I do not believe that this function was extensively tested with Dynamics CRM 2015 however, so it is possible that it has changed.

  17. Vijayesh says:

    Hi,

    I am trying to do new integration with dynamics nav 2013. When i am trying to configure the adapter settings. I am not able to see Micorsoft Dynamics CRM option. I can just view Microsoft Dynamics Nav and Dynamics CRM 2011.

    Note: The connector vers :Connector for Microsoft Dynamics NAV.msi (3.4.304.1)

  18. thehetz says:

    @Vijayesh – If you are integrating to any version of Dynamics CRM that is greater than Dynamics CRM 2011, you will need to use the Microsoft Dynamics CRM 2011 adapter.

  19. Vincent says:

    Hello,

    We (Microsoft partner) are having issues with the connector and NAV 2015 (latest builds). Every now and then a change is not picked up by the NAV service.

    A customer reported this issue to us. And in our test environment we experience the same thing. We don't have this issue with NAV 2009.

    With the help of fiddler, we can see that occasionally a change in a field value isn't picked by the NAV service (tested with contact and custom table).  

    Steps to reproduce: change the value of a field in NAV (integration record is updated), wait for the connector run (picks up & writes change), lookup the NAV service call in fiddler and look at the value, hence repeat. Occasionally the old value pops up instead of the (new) changed value.

    @thehetz

    Do you have any idea?

  20. thehetz says:

    @Vincent – I have not heard of this issue being reported before.  I would suggest contacting the Dynamics NAV support team in regards to this issue.

  21. Vincent says:

    @thehetz

    We found the problem after testing with a custom made program who read data using different NAV functions.

    When we install our solution we define multiple NAV (SOAP enabled) services using NAV 2015 administration for different purposes (same database):

    1) users (rtc client)

    2) connector

    3) (mobile) apps

    The problem is that a change made by using service 1 (user) is not directly picked up by service 2 (connector). There's a delay and sometimes it seems the change isn't noticed by service 2 at all. Because of the delay, when the connector runs the integration, it doesn't get the updated value(s) from service 2.

    The solution was to reconfigure the connector, set it to the same NAV (SOAP) service as the users are using (service 1). The moment we did this, updates where instant again.

    It seems that defining multiple NAV services is only viable when pointing to different databases.

  22. Bjorn says:

    A customer is considering upgrading from CRM 2011 to 2015. They are currently using connector 2.3 with NAV. I read on your site that 2.3 supports 2013, but I am unable to find any information if 2015 is also supported. Do I have to install V3 CU4?

  23. thehetz says:

    @Bjorn – If they do upgrade to CRM 2015 then they will also need to upgrade Connector for Microsoft Dynamics to version 3.4.x.x.  This is the only version of Connector that supports CRM 2015.  There are upgrade instructions in this post.

  24. MarjanC says:

    Can you please clarify something for me? Is it possible to integrate NAV 2015 and CRM 2011 with any version of the connector? If yes, which one?

    This article starts with:

    'Support for Microsoft Dynamics CRM 2015 is the primary new feature in Connector for Microsoft Dynamics V3 CU4 (3.4.304.1)'

    Then the important release info starts with:

    'This version of Connector NO LONGER supports integrations with CRM 2011 or CRM 4.0. '  

    And then it says:

    'Creating a new integration to CRM 2011?  Then you will need to use the CU 3 version of Connector which is still available at the download sites listed below.'

  25. thehetz says:

    @MarjanC – In order to create integrations with CRM 2011 and any version of the supported ERPs, you will need to use CU 3 for Connector.  For NAV, if you click on the Connector for Microsoft Dynamics NAV link in the post and then log into Customer Source, you will see the CU 3 download in the Downloads section:

    Connector for Microsoft Dynamics NAV.msi (3.3.1007.1)

  26. Bjorn says:

    Hi,

    I am getting an error when creating a product family in CRM 2015: Microsoft.Dynamics.Integration.Adapters.Crm2011.Plugin.ProductCreateUpdateEventHandler: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. I tried to upgrade the solution, currently 1.0.1603.3, to 1.0.1603.5 that was found in the installation folder, to see if that could be the issue. But the import fails with customeraddress and error: You cannot complete this action for this component because of the configuration of its managed properties.

    Please advise. Is updating to .5 necessary to fix the KeyNotFound exception?

  27. thehetz says:

    @Bjorn – Yes, version 1.0.1603.5 of the solution is required for interoperation with Dynamics CRM 2015.  I believe that it will address the issue that you are running into with product bundles.  If you have followed the upgrade instructions above exactly and are still running into the customeraddress exception that you list below, then it may mean that there are other customizations (un-managed) to that entity.  I would suggest logging a support incident if this is the case.

  28. Jonathan says:

    Is it just me or does the download for the GP connector not work?  Also, does it actually support GP 2010?  Here in the release notes, it says it does, but on the linked download page, it says GP 2013 is the minimum version.

  29. thehetz says:

    @Jonathan – Thanks for pointing this out.  Dynamics GP 2010 is out of mainstream support and so are integration to it which use Connector.  That is why I does not appear on the download page.  This blog post will be updated to reflect that.  I will also look into the download link on Customer source, which should be working.

  30. thehetz says:

    I have confirmed that the Connector for Dynamics GP download is working in Customer Source.  If you are internal to Microsoft, you can contact me directly as internal resources sometimes have issues downloading from CS / PS.

  31. Jonathan says:

    @thehetz

    Thanks for that clarification.  Makes sense to me. 🙂

    As for the download link, I'm an external customer accessing through CustomerSource and it is still not working for me.  The link refers to (mbs2.microsoft.com/fileexchange) This is the error I get:

    Our apologies…An unexpected error occurred.

    In order to resolve this issue as quickly as possible, please contact support and reference error ID: 57c6999a-8bc1-4987-a721-1618ba4e0b8a.

Skip to main content