How to connect Microsoft Dynamics CRM with SharePoint

This "how-to-connect" documentation will explain the initial configuration of an example connection from Microsoft Dynamics CRM to a SharePoint Online List in Office 365. We will be synchronizing data stored in Microsoft Dynamics CRM.

 

This guide presupposes that you have installed the Layer2 Cloud Connector and that you are familiar with its basic functionality. The Layer2 Cloud Connector User Documentation will provide you with all necessary information.

 

 

Contents

1. Configuring Microsoft Dynamics CRM

2. Configuring the Layer2 Cloud Connector

2.1 Creating a new connection

2.2 Configuring the Data Entity 1

2.3 Configuring the Data Entity 2

2.4 Running your connection

3. Hints and known issues

3.1 Connection direction

3.2 Data model

3.3 Inserting new Items

1. Configuring Microsoft Dynamics CRM

To connect to your Microsoft Dynamics CRM you only need the URL from your CRM and an account with the rights to connect to it. You can get this information with your system administrator.

 

2. Configuring the Layer2 Cloud Connector

2.1. Creating a new connection

Create a new connection by using the Create New Connection option in the Actions pane (right-hand side). The new connection will appear at the bottom of the Connection Manager List (left-hand side). Click on your newly created connection to open the connection configuration settings.

 

Choose a meaningful name for your connection and replace the current "New Connection" Connection Title with it.

 

Connections to Microsoft Dynamics CRM can be bi-directional. An initial connection should always be uni-directional to assure that both data entities are identical before switching to bi-directional. Therefore, choose Left to Right as Direction. You can change this setting after your initial synchronization finished successfully.

 

Step 1 Microsoft CRM connection setup.png

 

 

2.2. Configuring the Data Entity 1

We will now set up our Data Entities. Go to the data entity “Data Entity 1” to open the configuration settings.

 

Choose a Data Entity Title. It is recommended to give your entities meaningful names to maintain an overview when you decide to set up multiple connections.

 

Select the Data Provider for Microsoft Dynamics CRM from the data provider list. You can search for Microsoft Dynamics CRM by typing into the selection box.

 

Step 2 Microsoft CRM integration source setup.png

 

For the Connection String, we need the information mentioned in step 1. You can copy the below connection string and adjust it to match your gathered information. Use the Verify Connection String option to evaluate if the provided connection string is valid.

 

 

URL=https://yourcompany.crm4.dynamics.com/main.aspx;sales@layer2.pro;" this property should describe the user you wish to connect to SharePoint to. 

 

Enter the password that belongs to the user account used in the connection string into the Password field. Save your changes by using the right-hand pane option Save Changes.

 

Step 3 Microsoft CRM integration target setup.png

 

In the next step, we will configure our mapping settings. Click on the Mappings option on the left-hand pane. If your fields from SharePoint are named identical to the fields from your source system, the Enable Auto Mapping option will match those columns. Disabling this option allows you to match your columns as needed. We enabled auto-mapping in our setup. Save your changes by using the right-hand pane option Save Changes.

 

Step 4 Microsoft CRM integration mapping.png

 

2.4. Running your connection

To run your connection switch back to the main connection configuration node and use the Run Now Button located on the bottom of the setup page. The Run Synchronization Toolbox will also display the synchronization process. 

 

Step 5 Microsoft CRM data integration start.png

 

Below is a data preview of the information we have accessed in our source entity:

 

Microsoft CRM integration ready.png

 

This will be the result in our SharePoint Online list after our initial successful synchronization:

 

Finished Microsoft CRM integration.png

 

If you want to use a bi-directional synchronization, you can now switch your connection direction after our first initial synchronization run finished successfully. See section 3.1 for further information.

3. Hints and known issues

 

3.1. Connection direction

As far as tested, this connection supports uni-directional as well as bi-directional synchronizations. 

 

After adjusting the direction to bi-directional, you should check your Mappings settings again because some systems might include read-only columns that cannot be mapped directly.

 

We also recommend choosing a Conflict Resolution that matches your environment`s needs. You can find out more about the different conflict resolutions in our Layer2 Cloud Connector User Documentation.

3.2. Data model

To see all the tables and views you can access with the Microsoft Dynamics CRM provider, use these queries in the Select Statement:

 

 

SELECT * FROM sys_tables

 

SELECT * FROM sys_views

 

 

If there are more tables or views available, you can load them with the option "load more" in the popup window.

 

3.3. Inserting new Items

If you insert new items in the CRM in some cases GUIDs must be provided. You can use the Cloud Connector replication key settings to generate these GUIDs automatically. For example, to provide an accountid, set this name to the replication key settings of the data entity.

 

 

 

↑Top

Search for more data integration & synchronization solutions

Icon of Contact us - Chat - Layer2

Any Questions?

Contact us directly to discuss your specific requirements, help you with purchasing, or with any other questions.

 

Icon for Layer2 Solutions Finder- Layer2

About the Layer2 Cloud Connector

Get more information about the Layer2 Cloud Connector on the product page.

 

 

Icon for Layer2 Solutions Finder- Layer2

Register for a free trial

Get a free trial of the Layer2 Cloud Connector after a short registration.

 

 

© 2023 Layer Two Pte. Ltd.