Organization data service (OData v2 REST endpoint) deprecated

Organization data service (OData v2 REST endpoint) deprecated | Blog

Dec 03, 2015 Murali Narayanan

Organization data service (OData v2 REST endpoint) deprecated

The OData endpoint uses the Open Data protocol. This protocol implements a “RESTful” design pattern. REST represents Representational State Transfer. REST is an architectural style in which every resource is addressed by using a unique URI. In Microsoft Dynamics CRM, Odata endpoints are enabled as part of Organization data service. This was introduced with CRM 2011. The capability to perform asynchronous operations makes REST well suited for web resources and scripts used in Microsoft Dynamics CRM 2015 and Microsoft Dynamics CRM Online 2015 Update.

CRM Online 2015 update released Web API as a preview feature and now it is released with CRM 2016.

The new Web API provides better capabilities over the organization data service introduced with Microsoft Dynamics CRM 2011. Microsoft recommend any new code for this version use the Web API instead of the organization data service. Microsoft is going to deprecate the organization data service with this release The organization data service, also known as the REST endpoint or the OData endpoint, will remain in the application for the foreseeable future to support backward capability.

Web API is located at [organization uri]/api/data/v8.0/

We can perform all operations using HTTP requests with the Web API

Limitations of Web API

  • Cannot filter queries based on the value of a navigation property
  • Missing functions and actions for some organization service messages
  • Error when querying self-referential many-to-many relationships
  • When calling actions with entity collection parameters as well as other parameters, a collection parameter must be passed as the last parameter in the body
  • $select on some $expand expressions may be ignored
  • Cannot retrieve unpublished metadata
  • Single-Valued navigation properties may not be returned from a $expand query of they have a null value
  • FetchXML queries linked to activitypointer may not include linked fields
  • Null-valued properties may not be returned in expanded navigation property results

For detailed description refer here : https://msdn.microsoft.com/en-us/library/mt628816.aspx

About Author

Never Miss News

Want to implement Dynamics 365?


We have plans which will meet your needs, and if not we can tweak them around a bit too!

Just leave your details below and we will get back to you real soon!
Field will not be visible to web visitor