How to connect OnePageCRM with SharePoint

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

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 OnePageCRM

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

1. Configuring OnePageCRM

Go to your OnePageCRM and click on Apps / All integrations.

Scroll the page down and under Utilities click on API Developer Access.

Open Configuration to see and copy the User ID and API key values.

These values must be base64 encoded. Paste them like this userid:apikey and use a base64 service like this to generate the value and copy it.

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 OnePageCRM can be uni-directional only. An initial connection should always be uni-directional to assure that both data entities are identical. Therefore, choose Left to Right as Direction.

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 JSON from the data provider list. You can search for JSON by typing into the selection box.

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.

URI=https://app.onepagecrm.com/api/v3/contacts;FlattenArrays=1;CustomHeaders=Accept:*/*Authorization: Basic yourbase64encoded;	

• "URI=https://app.onepagecrm.com/api/v3/endpoint;" this property points to the endpoint we are connecting to. Use the OnePageCRM API to see more endpoints.
• "CustomHeaders=Accept:*/*(CLRF)Authorization: Basic yourbase64encoded;" between the value */* and Authorization the ENTER (CRLF - carriage return and line feed) is used to separate the properties. Press ENTER after */*.
• "FlattenArrays=1;" this property can be used to flatten the elements of nested arrays into columns of their own. It is an optional parameter that delivers the best results for us if set to 1. 

The Select Statement text box is used to define specific data queries. We will be gathering Contacts from the JSON answer with no empty ID's. You can copy the below select statement and adjust it to match your needs. Save your changes by using the right-hand pane option Save Changes.

SELECT * FROM json WHERE [next_action.contact_id] <> ''

To check if all necessary columns are received, you can use the Preview Data option on the right-hand pane which will provide you with a pop-up window showing your sample data from your OnePageCRM entity.

2.3. Configuring the Data Entity 2

We are going to send the data to a custom SharePoint Online list. It's required that you set up this list prior to the next steps. Your list should contain matching columns according to your source entity.

Use the left-hand pane to switch to the data entity "Data Entity 2". We will be using the Layer2 SharePoint Provider for this setup. 

For more information about the SharePoint provider visit:

https://www.layer2solutions.com/support/cloud-connector-faqs/layer2-csom-sharepoint-ado-net-provider.

You can copy the below Connection String which contains the minimum of required properties to connect to your custom SharePoint Online list.

URL=https://your_custom_sharepoint_list_url/AllItems.aspx;Authentication=Microsoft_Modern;

• "URL=https://your_custom_sharepoint_url/AllItems.aspx;" this property defines the URL of your custom list that will be addressed.
• "Authentication=Microsoft_Modern;" this property will determine the authentication method used. Microsoft_Moddern is the default authentication method to access Microsoft Office 365 / SharePoint Online and should work in most cases, even if the SharePoint site is connected to an ADFS. This authentication does not need any further connection string settings, other than the URL of the connected system.

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.

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.

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. 

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

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

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 only.

3.2. Data model

To see all the available endpoints from the OnePageCRM visit the API page here.

↑Top