Deploying the Instance Adapter - microsoft/Instance-Adapter-for-Microsoft-Dynamics-CRM GitHub Wiki
- Install Connector for Microsoft Dynamics for any of the supported ERP systems.
- Open Connector for Microsoft Dynamics. Click “Apply” on the Register Adapters dialog to apply blank settings for the adapters that are currently installed, and then close Connector.
- Open the installation directory for Microsoft Dynamics. By default, this is :\Program files (x86)\Microsoft Dynamics\Microsoft Dynamics Adapter.
- Extract the Microsoft Dynamics CRM 2011 Instance Adapter.zip file to this installation directory. Note: In the Connector installation directory, in the Adapters folder, a new folder is created that is named Microsoft.Dynamics.Integration.Adapters.DynamicCrm. This new folder also contains the sub-folder, ObjectConfig.
- In the installation directory for Connector for Microsoft Dynamics, open the Adapters folder, and then open Microsoft.Dynamics.Integration.Adapters.DynamicCrm. Right-click Microsoft.Dynamics.Integration.Adapters.DynamicCrm.dll, and then select Properties.
- Select the Security tab. If options to block or unblock the dll are displayed, verify that the Unblocked option is selected. Note: The options to block or unblock might appear on the general tab of the properties dialog, in the security section. Note: If you are using version 3.0.217.1 or later of Connector for Microsoft Dynamics, you will need to re-start the Connector for Microsoft Dynamics service at this point.
- Open Connector for Microsoft Dynamics and enter the settings for the Microsoft Dynamics CRM 2011 Source and Microsoft Dynamics CRM 2011 Destination adapters and Click “Apply” on the Register Adapters dialog to apply the settings. Note: The user that is specified to connect to the Microsoft Dynamics CRM source and destination instances should be in the system administrator role in the Microsoft Dynamics CRM organizations that are to be integrated. Note: The source and destination servers can be the same server.
- Run the Configuration Utility for each integration adapter and select the organization to integrate.
- Select the entities to integrate by selecting them from the list of entities or choose “Select All” and click “Next”. Note: To integrate custom entities between the source and destination servers, the customizations and loaded solutions in the source and destination servers must be same.
- On the final screen of the Configuration Utility click “Configure”.
- Click the “New Integration” button and select the Blank option.
- In the Application 1 field, select the Microsoft Dynamics CRM 2011 Adapter Source. In the Application 2 field, select the Microsoft Dynamics CRM 2011 Adapter Destination.
- Select the organizations to integrate and click “Create”.
- Create maps for integration. Note: It is recommended that you create a Picklist to Picklist map first, and run this map before other maps. This ensures that Picklist values are synchronized between the servers before other data is integrated.
- To ensure that all source fields are mapped to all destination fields in maps, enter “\” in the Mapping field at the root level of each map.
When integrating data between two systems, it’s important to run your maps in a specific order to avoid errors due to dependencies within the maps. Currently, the Connector does not offer a mechanism for automatic ordering, so the task of understanding the proper order to run the maps in falls on the implementer.
Picklists
- What the Picklist integration does
Adds any options to existing optionsets on the destination organization that are present in the source organization and not in the destination
Creates new global optionsets if they do not already exist on the destination organization.
- What the Picklist integration does not do
Create new local optionsets on entities
Business Units
Business units in the source and destination organizations must have the same values for their “name” attribute in order for them to be matched properly and these units need to be created prior to running the integration
Users
System Users will also need to have the same values for their “fullname” attribute in order to be matched and referenced properly and these users should be created prior to running the integration
Teams
Require that business units and system users be setup prior to integration
Security Roles
Require that business units and system users be setup prior to integration
Field Security Roles
Require that teams and system users be setup prior to integration
- Connector for Microsoft Dynamics blog: http://blogs.msdn.com/b/dynamicsconnector
- Connector for Microsoft Dynamics user guides: http://www.microsoft.com/en-us/download/details.aspx?id=10381
- Connector for Microsoft Dynamics installation video: http://youtu.be/Tl9b0qMumJk