We have developed our data integration layer using Entity framework 6 and Microsoft.AspNet.WebApi.5.0.0-rc1.

One of the client application is getting below error while updating an entity "This service doesn't support OData requests in the form '~/entityset/key'". Our EntityController implements the protected override GetEntityByKey([FromODataUri] long key) method. Request header in Fiddler shows x-HTTP-Method: Merge. Your help is Appreciated.

Thanks for sharing , But there are a broken links in this articles ,such as :-

"For more information, see Create a Read-Only OData Endpoint."

And

"For more information, see Supporting OData CRUD Operations."

also , OData.rog Documentation has a lot of broken links too.

Thanks for fixing these links :)

]]>Comment Posted by Eugene Gubenkovhttp://asp.net/web-api/overview/odata-support-in-aspnet-web-api/odata-routing-conventionsMon, 08 Sep 2014 09:11:03 GMT00000000-0000-0000-0000000033602I've created Custom routing convention for following template: "~/entityset/key/property" to provide raw properties' values, but to handle all possible property types I have to return object from Action method and this results in empty response.

]]>Comment Posted by christuttyhttp://asp.net/web-api/overview/odata-support-in-aspnet-web-api/odata-routing-conventionsTue, 20 Jan 2015 23:55:59 GMT00000000-0000-0000-0000000035864Portions of this article are specific to OData 3, in particular the section on "Creating and Deleting Links" but it's in the generic OData group, suggesting that it's correct for both OData 3 and OData 4.

I lost some time trying to make urls like DELETE /Products(1)/$links/Supplier work with an OData 4 service before realising that I should be using DELETE /Suppliers(key)/Product/$ref. The "Entity Relations in OData v4" article explains this difference and should be linked as well.