Why does my OData v4 API work for ?$filter=contains, but not ?$filter=field eq ‘val’?
I’ve written some OData V4 APIs to pull data from a local SQL database. I’m using curl to query the API. The APIs are ASP.NET and deployed on an IIS server.
I’ve written some OData V4 APIs to pull data from a local SQL database. I’m using curl to query the API. The APIs are ASP.NET and deployed on an IIS server.
I’m using WebAPI 2.2 and Microsoft.AspNet.OData 5.7.0 to create an OData service that supports paging.
This problem is affecting my ASP.Net WebApi Patch method which looks a lot like this:
I followed this asp.net tutorial by Mike Wasson, and managed to set up the related entities just fine, but when I applied this logic to my project the more complex entity relations (in that there are more of them; that’s the only difference) wouldn’t succeed in an OData call, I got a 404 with this payload:
Using Web API and OData, I have a service which exposes Data Transfer Objects instead of the Entity Framework entities.
for my WebAPI OData application, im trying to give my client (browser) the decision what format the data output should be. as $format is not implemented yet in WebAPI OData, im using Raghuramn’s example here: https://gist.github.com/raghuramn/5556691
I need to change the way OData serializes DateTime and DateTimeOffset.
I am new to this so i will start with the code and after that i will explain.
The problem is this
I have 2 web applications.
The first web application contains ASP.NET web pages and used a Membership provider for authentication.
The second web application is strictly an OData WEB API site that requires authentication.