What is OData? OData is short for Open Data Protocol. Microsoft Dynamics CRM 2013 and Microsoft Dynamics CRM Online uses their Windows Communication Foundation to provide this OData connection to the endpoint. The new OData Feature is part of Microsoft Dynamics GP 2016. This feature allows you to deploy an OData service to your employees to build reports developed through Power BI desktop, Excel, or any application compatible to deploy this service.
The OData service creates an end URL that will connect when we choose to utilize it in building reports. It also handles authentication of users to ensure they have access to the requested data. It is similar in requirements to Web Clients and companions application services. It is a group of specifications that define its core concepts and define additional optional extensions.
|[O Data: URI]||Conventions for constructing URIs to identify the resources and metadata exposed by an OData service.|
|[O Data: Terms]||Glossary of terms used by the protocol|
|[O Data: Operations]||
Defines the request types (retrieve, insert, update, delete, etc.) and associated responses used by the OData protocol.
An implementation can support some or all of the request types.
|[O Data: ATOM]||Defines an Atom Pub representation for the payload of an OData request/response.|
|[O Data:JSON]||Defines a JSON representation for the payload of an OData request/response.|
|[O Data: Batch]|| Extends the O Data Operations specification to define a mechanism to enable a client of a data service to “batch”
a group of requests and send that group/batch to the O Data service in a single HTTP request.
This protocol is designed so that any form of its implementation needs only as much specification as required in the required case. Simple OData services may consist of just a feed. More complicated services can have multiple feeds, it is useful to expose a service document that lists all the top-level feeds so clients can discover them and find out the addresses of each of them. The Open Data Protocol does not define new authentication or authorization schemes. Instead, those who implement the services may use the authentication and authorization technologies that fit best with their scenario. The use of authentication mechanisms to prevent the insertion or editing of resources exposed by an OData service by unknown or unauthorized clients is recommended.