Layer2 Data Provider for OData: Specifications for Cloud Connector
Cloud Connector for SharePoint can be used to
connect almost any external data sources to native SharePoint lists and
libraries, for example via the OData protocol as used by many applications, e.g.
SAP or Microsoft CRM/ERP systems. This FAQ gives the full specifications of the
Layer2 Data Provider for OData that is fully included in the
The Layer2 Data Provider for OData can connect data sources via
the OData protocol. The Open Data
Protocol (OData) is a Web protocol for querying and updating data via web
services. OData is being used to expose and access information from a variety of
sources including, but not limited to, relational databases, file systems,
content management systems and traditional Web sites.
Fig. You can use the OData.org demo services to verify the connector.
Normally, an OData request is presented in a single URL. Layer2 OData provider
splits the select portion and the data collection URL portion to present them as
a connection string and a separate select or query statement.
the Service Root URL for the OData source. The service root URL identifies the
root of an OData service. The resource identified by this URL MUST be an AtomPub
Service Document (as specified in [RFC5023]) and follow the OData
conventions for AtomPub Service Documents (or an alternate representation of an
Atom Service Document, if a different format is requested).
Format specifies such an alternate JSON-based representation of a service
document. The service document is required to be returned from the root of an
OData service to provide clients with a simple mechanism to enumerate all of the
collections of resources available for the data service. This information is
The resource path section of an URL
identifies the resource to be interacted with (such as Customers, a single
Customer, Orders related to Customers in London, etc.). The resource path
enables any aspect of the data model (collections of entities, a single entity,
properties, Links, service operations, etc.) exposed by an OData service to be
This setting specifies how the Cloud
Connector authenticates against the OData source. It can be one of the
This is the default value and
used to connect anonymous resources.
authentication cookie has been created using the cookie manager, this
authentication method can be configured to authenticate by using the
authentication cookies. (See The Cookie Manager for more
You can use Windows AD
authentication to login. Please provide user name and password as well, e.g.
Form Based Authentication (FBA) with username and password parameters
These methods are Dynamics CRM-specific for connecting to
their OData service:
to Microsoft Dynamics CRM Online. Username and password parameters
This is the default authentication method to access Microsoft Dynamics CRM Online instances and
works in most cases. This authentication does not need any further connection-string settings, other than the URL of the
connected system. The authentication needs to be setup in the UI, for more information check the Layer2 Cloud Connector User Documentation.
For connecting to an
Microsoft Dynamics CRM Online instance that uses ADFS. Username, Onlineuser, and
password parametesr required. For example: "username=myDomain\myUserName;
authentication for use with the NextCRM system, but also works with many
other Online CRM providers (online and on-premises). Username and password
For use with
systems that have ADFS on-premises authentications that require an NTLM
handshake to happen. Username and password parameters required.
See below for connection string
A Select statement for the Layer2 Data Provider for OData refers to the
query options section of an OData URL which is specified to control the amount
and order of the data requested. All OData services MUST follow the query string
parsing and construction rules defined in OData documentation section and its
subsections. Some services, like Dynamics CRM, do not support all type of
queries (see the system-specific documentation about their OData service for
more information). See below for examples.