This document discusses using the OData connector to connect to and integrate with OData services. It begins with an overview of OData and common data providers like ERP systems. Key points covered include features of the OData connector, limitations of working with specific ERP OData implementations, and tips for using the connector successfully. Examples are provided of querying Dynamics CRM and configuring for Dynamics NAV via the OData connector.

1. OData Connector
Power of Programming

2. Abstract
Do you want the power of programming directly against OData services? – Odata is
increasingly used by major CRM and ERP vendors as the preferred method to consume
data. In this session we will discuss how to connect to an OData service and view all of
the entity sets exposed. We will cover some of the challenges and benefits of using the
new OData connector in your integration design.

3. What is Odata?
Open Data
Protocol (OData)
Open protocol allows the
creation and
consumption of
queryable and
interoperable restful APIs
Microsoft Centric
Provides database-like
access to your data –
“ODBC for the Web”

4. Data Providers
Private Apps SQL SQL Azure
Azure Data
Marketplace
Data.gov

5. ERP
AX Odata NAV GP SL
SAP Netsuite Accumatica

6. Why Do I Care About Odata?
Easy
Azure Data
Marketplace
Microsoft
ERP
Direction to
Odata

9. ERP Implications
Augment Customer Data
Data Enhancement
Not all support CRUD operations

10. ERP direction regarding OData
Implementation varies greatly between all the apps.
Some are "fully baked" api's great for querying and
interacting with app
Microsoft has indicated that every ERP system will
have ubiquitous OData hooks

11. Scribe Online oData Connector
Features and Limits
OData protocol version 3.0
Delete Operation
Optimistic Concurrency

12. OData Metadata Not Supported
Edm.Geography
Edm.GeographyPoint
Edm.GeographyLineString
Edm.GeographyPolygon
Edm.GeographyMultiPoint
Edm.GeographyMultiLineString

13. Dynamics CRM: Query -
Each time that you
retrieve records, only the
top 50 records in your
query are returned

14. Odata Integration Pallette

15. Update Replace
A replacement update issues a PUT request. The OData service replaces all
property values with those specified in the request.
Any properties not included in the request (i.e. unmapped fields) are either
cleared or set to their default values. Any data in fields with unsupported data
types is lost.

16. Optimistic Concurrency = Record Locking Lite
Entity Tags (ETag) to determine how to update or delete
data The OData Connector exposes these ETags as fields.
The ETag field is available as a source and target
Optimistic Concurrency is optional

17. Batch Processing
The OData Connector supports batch
processing if your OData service also
supports batch processing. The number
of records allowed per batch will vary
depending on the OData service.

18. Update Patch And Update Merge
The OData service replaces exactly
those property values that are specified
in the request (i.e. mapped fields). Any
properties not included in the request
are not altered.

19. Conditional Success
When you insert or update a
record, some services may
indicate success but also return
error information in the response

20. Integration in Action

23. NAV Configuration

27. NAV Specific Limits
Filters OK
Querying related entities through joins are unsupported –.
What fields are Exposed?
http://localhost:7048/DynamicsNAV70/OData/$metadata

28. Tips/Tricks/Gottcha’s
If you try to use an operation that is not
implemented in your OData service, you may see an
error message.
Basic Authentication only (a Scribe limitation to not
support OAuth with OData connector)