Connector for Microsoft Dynamics V3 CU 3 released

Better support for Microsoft Dynamics CRM 2013 SP 1 (6.1) and Microsoft Dynamics NAV 2013 multi-tenant deployments are the primary new features in Connector for Microsoft Dynamics V3 CU3 (3.3.514.1) which was posted today, June 18th 2014.

Additional new features with this release include:

  • Support for Microsoft Dynamics CRM 2013 SP 1, which requires the updated Microsoft Dynamics CRM solutions included in this release (1.0.1603.4)
    • The workaround listed in this post is not required if using this release of Connector for Microsoft Dynamics to integrate to a new Microsoft Dynamics CRM 2013 SP 1 organization
  • Ability to add addresses to accounts and contacts in CRM that previously did have addresses associated to them
  • Microsoft Dynamics NAV companies that have special characters in their names are better supported
  • The required .NET framework versions (3.5 and 4.5.1) are checked for during installation
  • Support for re-creating Microsoft Dynamics AX customer addresses that have been deleted in Microsoft Dynamics AX and Microsoft Dynamics CRM previously
  • Support for upgrading Connector for Microsoft Dynamics installations on case-sensitive Microsoft SQL server instances

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

  • Connector for Microsoft Dynamics AX
    • If you have applied Microsoft Dynamics AX 2012 R2 CU 6 or later or if you are targeting Microsoft Dynamics AX 2012 R3, an XPO is no longer needed.  You can run the ConnectorHelper class that is included in CU 6 to accomplish the required setup tasks in Microsoft Dynamics AX 2012 R2.
    • Any release after Connector V3 CU2 (3.2.606.2) will support Microsoft Dynamics AX 2012 R3
  • Connector for Microsoft Dynamics GP
    • All previously supported versions of Microsoft Dynamics GP 2010 and GP 2013 are supported as either new or existing integrations
    • Microsoft Dynamics GP 2013 R2 is fully supported as well
  • Connector for Microsoft Dynamics NAV
    • Microsoft Dynamics NAV 2013 R2 is supported with this release, however this release is not required for an integration to Microsoft Dynamics NAV.  Any release after Connector V2 RU1 ( will support Microsoft Dynamics NAV 2013  R2.
    • 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

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 for Microsoft Dynamics download pages.  The user guides that are available at the following location will be updated to their latest versions by Monday, June 23rd 2014.

Comments (18)

  1. Jasmina Whyte says:


    I just read in the NAV configuration guide that only Windows logons are supported for Microsoft Dynamics NAV 2009 and higher.

    We have following NAV scenario (that we would like to integrate):

    * NAV 2013 R2 installed on Azure

    * Microsoft Dynamic NAV password authentication

    * ClickOnce installation client

    Can you confirm that our scenario is not supported by Connector?

    Is there any workaround for our scenario?

    Is it planned for future versions to support NAV password authentication?

    Thank you,


  2. thehetz says:

    @Jasmina – Dynamics NAV auth is supported.  That update was missed in our documentation.  Enter the Dynamics NAV adapter settings as you normally do but do not specify the domain setting (leave it blank) and you should be able to connect to you Azure based services.

  3. Jasmina Whyte says:

    That worked! Thank you for quick response, you saved my day!

    One other thing that might be good to mention in the future releases of instructions:  In the adapter settings, I had to set base URL to start with https as we are using https protocol. This seems obvious but it is easy to omit and I did not notice it mentioned in instructions for NAV configuration (unless I missed it). Thanks!

  4. Michael Simonsen says:

    I am using NAV 2013 r2 in a multi-tenancy environment. When I try to setup the Adapter for NAV i type int the URL and Tenans Name as described but I get an error when I click the "Test Settings".

    Have you got any examples of the URL or some way to test the URL and Tenant before testing.

    Thank you


  5. thehetz says:

    @Michael – are you leaving the domain name blank if you are using NAV authorization?  What error are you getting?

  6. Michael Simonsen says:


    Adapter settings:…/iebYvN0I


  7. thehetz says:

    @Michael – it looks like the value for domain was not blank.  Try again but this time leave that value blank.

  8. Michael Simonsen says:

    @thehetz – I get exactly the same error if I don't type anything in the domain.

  9. thehetz says:

    @Michael – it could be an issue with a firewall or some other network configuration then.  I suggest contacting Dynamics support as I know that they have worked with multi-tenant Dynamics NAV integrations using Connector for Microsoft Dynamics in the past.

  10. Richard Gist says:

    @Michael Example would be

    * URL:…/WS

    * Tenant Name: Tenant1

    Make sure that integrations are enabled on each tenant and that the integration user is present and configured for that tenant.

  11. Kevin White says:

    It doesn't seem like the Dynamics CRM adapter (as in the one with source and destinations) is supported with this new version. Has anyone had trouble installing it?

  12. thehetz says:

    @Kevin – I assume you are referring to the Instance Adapter for Microsoft Dynamics CRM 2011, is that correct?  If so, what issue are you seeing?

  13. Peter Nørgaard says:


    We are having some issues when istalling Connector v. 3.3.514.1 I have followed the instructions, and checked for the right version of .NET 4 and installed Windows Indentity Foundation. It's installed on a 2012 R2 server. The installaiton runs fine, and we are able to start the Connector app., but not the CRM 2011 adapter configuration util., it crashes. I have noticed, that the Microsoft.Dynamics.Integration.Adapters.Crm2011.dll are missing from the Microsoft Dynamics/Microsoft Dynamics Adapter folder, where the other adapters are installed. We found the dll in another folder, and registred it, and another file in the folder, also copied the ObjectConfig folder to the Adapter folder. Now we can start the configuraiton util. Well, we started to integrate, some worked, a lot failed so we thought that it might be something with the installation, and started all over Again on a fresh server, but it's the same = Microsoft.Dynamics.Integration.Adapters.Crm2011.dll are missing from the Microsoft Dynamics/Microsoft Dynamics Adapter folder and configuration util are crashing.

    Any suggestions?

  14. Sumit Khanduri says:

    Hi could you tell me that "Do we need a separate license for Connector V3 CU2 or CU3?"

    and which architecture is best suited for integration of nav and CRM (e.g., 2-tier or 3-tier)? please reply ASAP


  15. thehetz says:

    @Sumit – You do not need a separate license for Connector for Microsoft Dynamics, as long as you have a license for any Dynamics ERP or CRM.  The architecture that you choose for your Dynamics NAV integration is up to you, Connector for Microsoft Dynamics will work with either deployment.

  16. Simon says:

    In the AXConfig document, it says:

    If you are using Microsoft Dynamics AX 2012:

    The computer where Connector for Microsoft Dynamics is installed must have the following components


     Microsoft Dynamics AX 2012 .NET Business Connector

     Cumulative Update 1 for Microsoft Dynamics AX 2012

    Is this really true? When did this change? We use a separate server for Connector for Microsoft Dynamics and it will connect to CRM/AX through their webservices – why would we need to install the Connector on the AX machine now that we updated it to version 3 CU 3?

  17. thehetz says:

    @Simon – the Dynamics AX 2012 adapter has always had these requirements, it does not need to be installed on the Dynamics AX 2012 server.  The machine where Connector is installed does need to have the Dynamics AX 2012 .NET Business Connector component installed on it.  This is so the Dynamics AX 2012 configuration utility and the Dynamics AX 2012 adapter can access the Dynamics AX 2012 metadata service.