Microsoft Dynamics CRM 2011 Instance Adapter Installation

System Requirements

Microsoft Dynamics CRM 2011 in any deployment

Connector for Microsoft Dynamics version 2.1.317.1 or greater, which can be obtained from
Customer Source at the following URL:
https://mbs.microsoft.com/customersource/productinformation/relatedproducts/MSDYN_Con
nectorforMicrosoftDynamics.
o The version of Connector for Microsoft Dynamics that you obtain can be for any of the
Microsoft Dynamics ERPs. If you currently use a Microsoft Dynamics ERP, we
recommend that you download the version of Connector for Microsoft Dynamics for
your Microsoft Dynamics ERP.
System users in the source and destination Microsoft Dynamics CRM organizations should have
the same full name attribute in order to preserve ownership across organizations.
o The Microsoft Dynamics CRM 2011 Instance adapter will look up references to system
user entities based on the fullname attribute and if a system user with the matching
fullname attribute is not found in the destination organization, it will use the
systemuserid of the system user specified in the Microsoft Dynamics CRM 2011
Destination adapter settings for this attribute.
If there are customizations that you wish to integrate data for, those customizations must be
present in both Microsoft Dynamics CRM systems before their data can be integrated using the
Microsoft Dynamics CRM 2011 Instance Adapter.

Installation and Configuration

1. Install Connector for Microsoft Dynamics for any of the supported ERP systems.
2. 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.
3. Open the installation directory for Microsoft Dynamics. By default, this is <Drive>:\Program files
(x86)\Microsoft Dynamics\Microsoft Dynamics Adapter. Extract the Microsoft Dynamics CRM
2011 Instance Adapter.zip file to this installation directory.

Microsoft

10/23/2012

4.

5.
6.

7.

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.
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 source and destination servers can be the same server.
Run the Configuration Utility for each integration adapter and select the organization to
integrate.

Microsoft

10/23/2012

8. 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.
9. On the final screen of the Configuration Utility click Configure.
10. Click the New Integration button and select the Blank option.
11. 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.

Microsoft

10/23/2012

12. Select the organizations to integrate and click Create.

13. Create maps for integration.

Note: We recommend 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.
14. 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.

Notes

When integrating data between two systems, its 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.

Microsoft

10/23/2012

Picklists
o 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.
o What the Picklist integration does not do
Create new local optionsets on entities.
Business Units
o 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
o 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.

Additional Resources

Connector for Microsoft Dynamics blog: http://blogs.msdn.com/b/dynamicsconector

Connector for Microsoft Dynamics user guides: http://www.microsoft.com/enus/download/details.aspx?id=10381
Connector for Microsoft Dynamics installation video: http://youtu.be/Tl9b0qMumJk

Microsoft

10/23/2012