​The Cloud Connector for Microsoft Office 365 and SharePoint connects almost any on-premise data source, e.g. ODBC, OLEDB, OData, Microsoft .NET based providers, Files (Excel, XML, CSV), SQL databases like SQL Server, Oracle, MySQL, IBM DB2, IBM AS/400, IBM Informix, Notes, SharePoint, Exchange, Active Directory, Navision, SAP and many more directly to native SharePoint lists and libraries in the Microsoft Cloud - or any other Microsoft SharePoint installation - in just minutes without any programming. For any questions please use the FAQ Web Form or contact [email protected] directly.

Office 365: How to sync external XML data with native SharePoint lists?

Integrating external XML data sources (e.g. from LOB applications) from file system or web requests with native SharePoint lists (e.g. news, contacts, tasks or custom lists) in Office 365, SharePoint Online or SharePoint can close some gaps using Microsoft SharePoint, on-premise or in the cloud. Please note: It's not only about displaying external data - it's about full integration with search, lookups, change notifications, workflows, enterprise metadata etc.

This FAQ gives a step-by-step example how to do this.

Prepare your external XML data source to integrate with Office 365

Let's take a sample XML, the well-known CD catalog. Think of it like an export from your LOB application, e.g. ERP, CRM or something like this.

Fig.: The screen shows a sample XML-based document to connect with a native SharePoint list.

Please note:

  • Almost any LOB system should be able to expose data in a format like this
  • XML files are supported as well as web requests (per URL)
  • You can query / filter data subsets later on using XPath

Setup your XML to SharerPoint connection

​With the Cloud Connector Connection Manager (a MMC snap-in) you have to setup:

1. the connection (e.g. uni-directional with overwrite, scheduling etc.),

2. the data source (your XML file or web request) and

3. the data destination (in SharePoint on-premise, SharePoint Online or Office 365. The list must be created manually before).

You can use auto mapping to connect the fields of both data entities by name or map fields manually.

See here for sample connection settings:

Fig.: Sample XML to Office 365 one-way connection.

Please note:

  • Bi-directional connections are not supported for XML data sources at this time.
  • If overwrite destination is enabled, non-matching entries in the destination are removed with initial sync.
  • Please enable scheduling later on, when all settings are verified and you have an idea of replication duration. Duration time depends on bandwidth, performance of source and destination, and number of entries in XML. Only changes are transferred later on.

Before running the connection, you have to define the data source and destination.

Fig.: The Layer2 XML Provider is used to connect to the data source, e.g. an XML web request.

Please note:

  • Select the Layer2 XML Provider
  • Enter the file path or URL to your XML data as connection string.
  • The provider offers a XPath-based query language to select your data subset from the XML data source after the FROM keyword in the select statement.
    Please read more about XPath here.
  • You can optionally select named attributes with the select statement, e.g. "Select TITLE, COUNTRY, ...)
  • Use the data preview to check out the result of your Xpath query. You can use any 3rd party XPath tool to test.
  • You have to enter a "primary key", some column with unique values in your query result.
  • Please verify all settings before save.

Next you have to define your data destination:

Fig.: Data destination sample, a list "XML" in the Office 365 cloud.

Please note

  • Use the Layer2 SharePoint CSOM Provider to connect to SharePoint on-premise, SharePoint Online or Office 365.
  • You have to create the destination list manually with all columns required to host your query data.
  • Read more about connection strings to connect to Office 365, SharePoint Online or SharePoint on-premise here. Please note that you can connect to any other data destination, e.g. to a SQL database.
  • There is no need to enter a primary key, the provider automatically uses the SharePoint item ID.

As a last step you have to setup the column / field mapping. You can use the auto-mapping feature (by field / column names) or map manually.


Fig.: Sample field / column mapping of data source and data destination.

If all settings are verified, please go to connection root and run the connection manually first. Please note, that it could take some time to transfer all nodes. You can take a look in your cloud list to see how it goes on.

See your XML data in the Office 365 SharePoint list

​Now take a look at your list now. All items are in there, after running the connection.

Fig.: Sample data destination in the Office 365 cloud.

Please note:

  • Selected items are transferred only, e.g. only items with country = "USA" in this sample.
  • Changed items are transferred only on update. That means, you can setup change notifications per-email or workflows in the cloud without any restrictions.
  • You can add additional "SharePoint only" data, e.g. attachments or managed metadata. It will be kept while items are updated.
  • You can do anything you can generally do with a SharePoint list - without any restrictions (e.g. search).
  • Don't forget to setup the background update, to keep data current in connection settings, e.g. with scheduled updates every hour or daily.

Next step: Download a FREE shareware edition of the connector

​For a complete Layer2 Data Provider for XML specification see here. You can download a free shareware edition of the Layer2 Cloud Connector for Office 365 and SharePoint after registration here.

Share this site on Xing
Share this site on Google+
Share this site on LinkedIn

Bringing the cloud a little closer: Very easy setup and a good selection of connector types available to integrate on-premise data and cloud based Sharepoint. Allows for some very interesting capabilities. Support is also quick to respond.

Frank Daske

Frank Daske

Business Development Manager
+49 (0) 40 28 41 12 - 30
[email protected]

Please note that the 011 exit code must be dialed first for all international calls made from the USA, Canada and Australia.

Related News

Layer2 now connects 100+ commonly used IT systems with Twitter via its Layer2 Cloud Connector

The Layer2 Cloud Connector is now able to connect Twitter to integrate data to a wide range of IT backend systems including Office 365, SharePoint, SQL, ERP/CRM.

New Microsoft Teams Connectors: Layer2 adds 100+ typically used backend systems

​The Layer2 Cloud Connector is now able to connect to Microsoft Teams to quickly integrate more than 100 IT backend systems including local SQL, ERP/CRM.
Related Downloads
PDF Image

Cloud Connector Instruction

Download this step-by-step instruction to connect and sync your corporate or cloud data sources bi-directional to any native SharePoint 2010/2013/2016 list or library, including Microsoft Office 365.
PDF Image

Feasibility Study: Connecting local SQL Server to SharePoint Online

The study compares different approaches for SharePoint Online data integration regarding performance, features, security and investment.
PDF Image

Flyer: Layer2 Partner Program

Partner with us as a software distributer, reseller or SharePoint, Office 365 or Azure service provider. We are offering a free Partner Program with up to 30% Discount, free NFR licenses etc. Please download for more.
PDF Image

Layer2 Case Study: Cloud Connector helps ChemWerth to integrate the Microsoft Office 365 Cloud

"The Cloud Connector’s interface is easy to understand and use. Anyone familiar with utilities in the Microsoft stack will be productive immediately. Our recommendation: The Layer2 Cloud Connector is a no brainer.”
NoDoc Image

Layer2 Cloud Connector PAD File

This XML-based PAD file offers a Layer2 Cloud Connector product description for resellers to download and publish.
PDF Image

Office 365: How to sync with MS Dynamics CRM

You can sync any CRM data with native lists in SharePoint on-prem or online to make it available offline with Outlook.
PDF Image

Office 365: How to sync with SAP?

You can connect SharePoint and Office 365 with SAP via NetWeaver and OData.
PDF Image

Office 365: How to sync your local file share?

When you are moving to the cloud, there are a lot of reasons to keep your local file system. But you don't have to miss the benefits of the cloud.
PDF Image

Product Flyer: Cloud Connector for Microsoft SharePoint & Office 365

Flyer with features, benefits & pricing info for download as PDF.
PDF Image

Product Flyer: SharePoint Online Local File Server Sync

You can centrally migrate, synchronize, or backup your local file server department shares and home drives very flexible with SharePoint Online to close known gaps and overcome limitations of the Microsoft OneDrive for Business client.
PDF Image

Solutions Flyer: Data Integration with SharePoint, Office 365 and 100+

FileMaker can be integrated with 100+ other sources codeless using the Layer2 Cloud Connector.
Related Links

Layer2 Cloud Connector Community Group @ LinkedIn

​Are you already @ LinkedIn? Please join the Cloud Connector Community Group to share your experience.

Microsoft Partner Story Book for Office 365 about Cloud Connector

​Know more about a Layer2 Cloud Connector customer reference at the Microsoft Office web site.

Purchase Layer2 Cloud Connector via ComponentSource

​ComponentSource has offices in the USA, UK and Japan supporting over 125,000+ Customers, in over 180 Countries. They are also an approved Federal Government supplier through the GSA Schedule.



Sign Up for Layer2 Product Newsletter

We keep you up-to-date about new Layer2 product releases, added features and fixed issues.