You have to create the SharePoint list to host your Salesforce data manually before connect. Please add appropiate fields or use pre-configured list types, e.g. contacts in this case.
Now you can connect the SharePoint data entity as follows:
- Data Entity Title: Enter as you want.
- Entity Type: Destination in case of an uni-directional connection. You can setup at the connection's page.
- Data Provider: Select Layer2 Provider for SharePoint to connect to SharePoint or Office 365.
- Connection String:
URL=<URL of SharePoint Site>
List=<your List name or title>. In this case a contact list "Contacts"
View=<your View name or title>. Not used in this case, but helpfull to provide certain fields only and sync more than 5.000 items.
Authentication=<Your Authentication Method>. Windows in this case, can also be "Office365" or "ADSF". See below for more details.
User ID=<userID> Your SharePoint Login
Password=<password> Your SharePoint password
- There is no select statement here, but views should be used instead of.
- No need to give a primary key here, SharePoint Item ID is used internally.
- While writing changes to your SharePoint list you can disable insert, update or delete operations, if required (e.g. for data aggregation or archiving).
You will find more details in the Layer2 Data Provider for SharePoint specification.
Please verify all settings and display the preview data. As a next step you can map your source data fields to columns in the data destination. In this sample you can't use auto-mapping (based on field names) because names are different in Salesforce and SharePoint. Please also note the mapping of the SharePoint Title field (required in SharePoint).
Fig.: Field / Column mapping between Salesforce and SharePoint
Now you are ready to run the first synchronization as follows:
Fig.: Manual synchronization between Salesforce and SharePoint (first run). You can sync changes automatically in background later on.
As expected contact items are inserted into SharePoint. In case of error messages follow the instructions, e.g. improve field mapping. Please note that the first sync can take a while, depending on amount of data. If all looks good, please run sync again. You should have no changes in SharePoint in case there were no changes in Salesforce. If you see changes (e.g. all items changed with each run) your configuration does not work as expected, e.g. because of invalid data type conversions. Please improve configuration (e.g. column types). When all works as expected, you can enable scheduling. Please make sure that your Layer2 Windows Service is up and running to process the changes in background. No need to have the Connection Manager open or being logged-in at the computer.
Fig.: Salesforce account data synchronized with SharePoint contacts.
In this sample SharePoint Server 2010 on-premises is used to connect to Salesforce, but it works in the same way with SharePoint Server 2013 (also with the free Foundation) or SharePoint Online, Office 365, OneDrive for Business - or almost any other data source.