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:
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 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.
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?
@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.
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!