Kennedy Kang'ethe
Kennedy Kang'ethe
@michalczerwinski Check this comment https://github.com/OData/AspNetCoreOData/issues/247#issuecomment-1068883361 I have a sample project that works https://github.com/KenitoInc/AspNetCoreOData8Net6 I hope that helps you resolve your issue
Another blog post that may assist https://devblogs.microsoft.com/odata/customizing-filter-for-spatial-data-in-asp-net-core-odata-8/
@icnocop Have you tried setting the statuscode before calling ExecuteAsync see this https://github.com/OData/WebApi/blob/0a23c07bfd74052a744e8607c9a0420d2790f3ef/src/Microsoft.AspNetCore.OData/Results/NotFoundODataResult.cs#L59-#L67
@Reena-Patel Was you issue resolved?
Did you try @xuzhg's suggestion?
@ClementeGao Was you issues resolved? If yes, we can close this issue
@karayanni Actions have "side effects" so are invoked by `POST` method. Functions have no "side effects" so are invoked by `GET` method.
@karayanni Did the information above help resolve your issue?
There is also a config that allows parameterless functions to work with no parantheses. Try the code below ```csharp builder.Services.AddControllers().AddOData(opt => { opt.AddRouteComponents("odata", EdmModel.GetEdmModel()).Count().OrderBy().Filter().Select().Expand(); opt.RouteOptions.EnableNonParenthesisForEmptyParameterFunction = true; }); ```
> @KenitoInc , shouldn't we consider just always allowing that to simplify the API/improve usability? Is there a specific reason to have this as a configurable option instead of just...