Connector for Microsoft Dynamics V3 (126.96.36.199) released today! This release includes a major update to the MSDI database and Connector for Microsoft Dynamics service, designed to improve efficiency of the service as well as making it easier for customers and developers to interact with it. This release also addresses some of the key suggestions that you have given us regarding your V2 RU 3 deployments. Additional features and updates are listed later in this post.
Release Highlights FAQ:
- Is it possible to save filters with my map(s)?
- Yes, with version 3, filters are saved with maps and are included when creating a map from a file that has a filter
- Do I have to always stop and restart the service every time I want to delete something or update the “Check for data modified after” time?
- No, stopping the service with every change isn’t required in version 3
- Can a developer directly interact with the service, say to change settings, create maps, or immediately force a map to run?
- Yes, developers have more flexibility in how they interact with the version 3 service
- Has the MSDI database schema changed at all?
- Yes, please be sure to backup your MSDI database before upgrading in the event that you need to roll back to a previous version
- Are the Connector for Microsoft Dynamics configuration settings still stored in the MSDI database?
- No, they have been moved to the ConnectorServiceHost.exe.config file in the Connector’s installation directory
Feature list (all of the features listed for all previous releases are still included):
- Filters are now saved with maps and are imported when creating a map from a file that has a filter saved in it
- When deleting an integration, site, or map the service no longer needs to be stopped and restarted
- When changing the “check for data modified after” date for a map, the service no longer needs to be stopped and restarted
- Connector for Microsoft Dynamics service is now a WCF service that is run inside of its own process host, allowing developers to programmatically interact with the service
- Maps can now be run “on demand” using the “RunMapNow()” API on the updated Connector for Microsoft Dynamics service. Stay tuned for a blog post demonstrating how to do this programmatically.
- System handle counts and memory consumption have been reduced for long running integrations
- Connector for Microsoft Dynamics client responsiveness has been improved
- Performance when integrating to Microsoft Dynamics CRM online has been increased
- The MSI now validates the SQL server version, as well as the other system requirements
- “Socket Connection was aborted” errors when integrating using WCF services are now avoided
- Supported Microsoft SQL Server versions have changed slightly:
- Microsoft SQL Server 2005 SP4
- Microsoft SQL Server 2008 SP2
- Microsoft SQL server 2008 R2
- Microsoft SQL Server 2012
- Supported Microsoft Windows Server versions:
- Microsoft Windows Server 2008 SP2
- Microsoft Windows Server 2008 R2 SP1
- Microsoft Windows Server 2012
- Connector for Microsoft Dynamics client no longer communicates directly with the MSDI database, rather it communicates exclusively with the Connector for Microsoft Dynamics service. This means that if you stop the service, the client will stop working as expected and must be closed and restarted after the service has been restarted. It also means that the ability to interact directly with the service from the Connector for Microsoft Dynamics client has been removed.
- After upgrading an existing Connector for Microsoft Dynamics installation to V3, you will need to re-enter the passwords that are listed in the adapter settings for the default settings and in the “Settings” node for any integrations that you created in a prior version of Connector for Microsoft Dynamics
- If you create new custom adapters using the Connector for Microsoft Dynamics SDK, after deploying those adapters to a V3 system you will need to restart the Connector for Microsoft Dynamics service (be sure to close the client first) to detect the new adapter on the system, with previous versions this restart was not required
- While we have made every effort to make the upgrade process as seamless as possible, we still encourage you to test the upgrade in a non-production environment first to ensure that all of your customizations continue to work as expected before moving the upgrade into production.
Note: if you are using Microsoft Dynamics CRM Online or are planning on upgrading your on-premises deployment to the update rollup 13 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 CustomerSource:
- Connector for Microsoft Dynamics AX
- The XPO that is required to enable support within Microsoft Dynamics AX 2012 requires that Cumulative Update 1 for Microsoft Dynamics AX 2012 be installed
- The XPO that is required to enable support within Microsoft Dynamics AX 2012 R2 is different than the XPO for Microsoft Dynamics AX 2012 and is listed as a separate download
- Microsoft Dynamics AX 2012 R2 CU 1 is fully supported
- Connector for Microsoft Dynamics GP
- This version no longer supports new integrations using Microsoft Dynamics GP 10.0, upgrades to existing integrations using Microsoft Dynamics GP 10.0 are supported
- All versions of Microsoft Dynamics GP 2010 and GP 2013 are still fully supported as either new or existing integrations
- Connector for Microsoft Dynamics NAV
- This version requires Microsoft Dynamics NAV hotfix 2597312 and hotfix 2721512 when integrating Microsoft Dynamics CRM with Microsoft Dynamics NAV 2009 R2
- 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.