​​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 on-premise installation - in just minutes without any programming. This article is about integration of the BOX.NET cloud service with SharePoint libraries to increase the value of file sharing with collaboration. For any questions please use the FAQ Web Form or contact [email protected] directly. Please note that you need Cloud Connector Version 4.2 and higher to connect.

How to integrate any SharePoint library with BOX.NET?

​Assuming you have a Box.NET account like this and want to add value to it by connecting a native SharePoint library on-premise or in the SharePoint Online / Office 365 cloud bi-directional without any coding for better collaboration using the Layer2 Cloud Connector.

BOX.NET-SharePoint-Integration-600.png 

Fig.: BOX.NET default sync folder to be replicated with a native SharePoint library.

As a first step sync your BOX.NET files to any local file system using the BOX.NET connector (available via BOX.NET). As a next step you can replicate files between the local file system and SharePoint.

BOX.NET-SharePoint-Integration-600-0.png 

Fig.: Local file system My Box folder to replicate with a SharePoint library.

1. Define your connection between BOX.NET and SharePoint

​First you have to define your connection between BOX.NET and SharePoint in the Layer2 Cloud Connector Connection Manager.

BOX.NET-SharePoint-Integration-600-1.png 

Fig.: Connection settings in the Cloud Connector Connection Manager.

Please note that uni-directional and bi-directional connections are supported. Start with scheduling disabled until all settings are verified. Use the Run Synchronization Toolbox to test.

2. Define the File System Data Entity and the SharePoint Library Data Entity

​Now you have to define both data entities to connect, the local file system and the SharePoint library. First define the file system data entity.

BOX.NET-SharePoint-Integration-600-2.png

Fig.: Sample file system data entity settings.

Please select the Layer2 Data Provider for File System and enter the root directory. In case of BOX.NET this looks like:

Directory=C:\Users\MyUser\Documents\My Box Files\

You don't need to enter any primary key or other additional settings. Please see here for additional options of this provider. Please verify the connection string and display data preview.

Now define the SharePoint library data entity settings.

 

BOX.NET-SharePoint-Integration-600-3.png

 Fig.: Sample SharePoint library data entity settings.

 
Please select the Layer2 Data Provider for SharePoint (CSOM) and enter the connection string to your library. Please create the library manually before connect. The connection should look like this (in case of an Office 365 connection):
 
 
Please see here for more options of this provider, e.g. authentication options and connection string samples for SharePoint on-premise. Please verify the connection string and display data preview.

3. Define Column Mapping

​As a next step you have to define the mapping between file attributes and SharePoint columns. You can use auto-mapping in this case for correct mapping. 

BOX.NET-SharePoint-Integration-600-4.png 
Fig.: Sample column mapping between file system and SharePoint.

 

Please note that file system user data cannot be assigned to SharePoint user columns, because different tokens are used on both sides. But you can assign user names to any additional text column in SharePoint, e.g. to a column "Source User". In some cases it makes sense to assign the source file path to any additional column as well, e.g. to a column "Source File Path". Please verify the mapping.

You are now ready to run the connection in the connection settings page. 

4. Make Use of your SharePoint Library connected to BOX.NET

​Now you can make use of your SharePoint library connected to BOX.NET.

BOX.NET-SharePoint-Integration-600-5.png 

 Fig.: Sample SharePoint library connected to BOX.NET.

Please note that you have all features of a native SharePoint library available:

  • You can sync back changes to BOX.NET if a bi-directional connection was configured. Only changed items are transferred.
  • You can use the default search to find the documents.
  • You can create additional SharePoint-only columns, e.g. for remarks, ranking, rating, enterprise metadata etc.
  • You can use change notifications per email or subscriptions via RSS to stay in contact and inform your users about external changes.
  • You can start business workflows on external data change.

To make it short: You can do all what you can do with SharePoint.

Next Steps: Download and evaluate the Layer2 Cloud Connector for free

​​​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 on-premise installation - in just minutes without any programming. You can download a free Shareware Edition after registration on product page.
Share this site on Xing
Share this site on Google+
Share this site on LinkedIn

The Layer2 Cloud Connector solved all of our most pressing needs regarding external data-sources and data-flow integration for our Sharepoint Online-based app development. One-way or bi-directional syncing are a breeze to set-up.

Contact
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

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.

Layer2 Office 365 and SharePoint integration now compatible to FIPS

The newest Layer2 Cloud Connector release is compatible to the Federal Information Processing Standards (FIPS) of the United States federal government regarding strong encryption.
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 local SharePoint?

You can replicate selected parts of your SharePoint intranet portal to the Office 365 / SharePoint Online cloud.
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.

 

cs-award-top-100-publisher-2014-15-large.gif

Sign Up for Layer2 Product Newsletter

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