Using OData sources with Business Connectivity Services in SharePoint 2013
Published: July 16, 2012
Learn how to get started creating external content types based on OData sources and using that data in SharePoint 2013 or Office 2013 components.
Applies to: SharePoint Server 2013
The Open Data protocol (OData) lets you access a data source, such as a database, by browsing to a specially constructed URL. This allows for a simplified approach for connecting to and working with data sources that are hosted within an organization.
The new OData connector enables SharePoint to communicate with OData providers.
In SharePoint 2013, Business Connectivity Services (BCS) can communicate with OData sources, or producers, without having to code directly to the OData source. Producers expose their data in a structured way via a web service. Some producers may allow updating of the underlying data, and some may allow only read access. For purposes of advertising what operations are available, the producer has a service document found at a specified URL endpoint. SharePoint is already a producer of OData. SharePoint list data is exposed as an OData source for any consumer that has the appropriate rights.
Examples of OData producers
The following are some examples of implementations of OData. These applications and services expose their data through the OData protocol.
SharePoint Foundation 2010
SharePoint Server 2010
Windows Azure Table Storage
Windows Azure Marketplace
SQL Server Reporting Services
Microsoft Dynamics CRM 2011
For a list of producers of OData services, see the Open Data Protocol website.
To develop OData-based external content types, you will need the following:
Visual Studio 2012
Office Developer Tools for Visual Studio 2012
For information about how to set up your development environment, see Start: Set up the development environment for SharePoint 2013.
For SharePoint to use the data exposed by a specific OData producer, an external content type must be created inside SharePoint. As with all SharePoint external content types, it contains all the connectivity information that is needed to connect and communicate with the external system.
Creating an external content type that uses an OData data source is similar to creating any external content type. You can use Visual Studio 2012 to automatically generate OData external content types. You merely provide the Representational State Transfer (REST) endpoint of the OData source when you create the external content type. For more information see How to: Create an external content type from an OData source in SharePoint 2013.