Performance improvements and key suggestions on Connector V3 deployments are the primary new features in Connector for Microsoft Dynamics V3 CU1 (220.127.116.11), which was posted today for download.
Additional new features with this release include:
To download this release for your Microsoft Dynamics ERP system, go to CustomerSource:
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.
Note: This release includes an update to the MSDI database that will mean any custom objects you have added to the database will be dropped, however this update will greatly improve the performance of the overall Connector system.
Can anyone offer clarification around Change Tracking and implications on the Connector for Dyanmics AX 2012 R2 - all documentation seems to point to the idea of simply '...select the Change Tracking option in Microsoft Dyanmics 2012' in order to enable or disable change tracking.
I understand from the documentation that Change Tracking must be disabled to successfully work with Dynamics AX 2012 R2 - however no documentation clearly dictates where Change Tracking should or should not be enabled - is it at the database level (if so which database), is it at the table level (if so which tables), is there a setting in the AIF parameters of AX 2012 R2?
The reason this needs clarified is for those who have recently upgraded to R2 and are not aware if change tracking was enabled at any stage by another developer on the instance of AX. Please provide clarification of where to look specifically for Change Tracking.
@Dillon - SQL change tracking needs to be enabled on the AX database within SQL server.
"If you have applied Microsoft Dynamics AX 2012 R2 CU 6 or later, an XPO is no longer needed. You can run the ConnectorHelper class that is included in this update to accomplish the required setup tasks in Microsoft Dynamics AX." Would it be possible to ensure this line is updated in all Config and Install documentaiton? I have just spent 4 days attempting to debug a metadata issue that was the source of this class not being run in AX 2012 R2 CU6.
Can you connect two CRM with the same ERP (only 1 connector and 3 adapters)?
@Dillion - yes we will get this updated ASAP in the documentation.
@Daniel - yes this would be possible. You would need to create two integrations using the same adapters (CRM and ERP). After you create the first integration you will need to change the default settings for the CRM adapter so that when you go to create the second integration the CRM adapter will connect to the second instance.
I tried upgrading Connector from V2 to V3.1. (AX 2009, CRM online 2013 just upgraded from 2011). When I open Connector client, get error saying "A service error has occurred. Please check your server error logs for details." I looked into Event Viewer, saw connector service error log.
Unexpected service error on call : www.microsoft.com/.../GetDefaultAdaptersWithSettings --- Exception Dump --- Caught Exception: [System.NullReferenceException] Object reference not set to an instance of an object. Stack trace: at
@Alan - Have you logged a support request on this? It is something that we have not seen before so I think that going through support would be the best option at this point.