John Gathogo

@ShvetsovAU Thank you for reporting this issue. I was able to reproduce it. Find my explanation below. This is currently not supported: ```csharp var res43ObjectIdList = dataSet4.Select(d1 => d1.ObjectId).ToList(); ```...

@Robelind The code in your client application won't currently work because OData WebAPI doesn't currently support deep inserts/updates. That feature is currently being worked on. However, you can still accomplish...

The Microsoft.Spatial types are not compatible with the spatial data types used in the database. For that reason, most customers are unable to use the types in the Microsoft.Spatial library...

Consider the following invalid cases too: - (ns.myType) - ns.myType) - (ns.myType

@dvkrish @AndrewZenith @closem90 Can you check out the sample shared by Sam here https://github.com/odata/aspnetcoreodata/issues/98#issuecomment-1917579319 and confirm if that helps?

In a case like this where an untyped numeric value is read as a decimal, there could be customers depending on this behaviour and changing that could lead to a...

Thank you @sliekens for reporting the feature gap. We'll triage it and add it to add it to our backlog. If you're in a position to contribute a pull request...

> Should this feature also be supported in CSDL JSON? @habbes Good catch. Made the relevant changes to ensure the facets get serialized for CSDL/JSON. The CSDL parser currently doesn't...

`ODataUrlValidationContext` class exposes a public `AddMessage` method for adding items to the `Messages` collection property. It therefore appears as an oversight or bad design for the `Messages` property to be...

@MrtnSys Confirmed that an exception is thrown if a property of type `IEnumerable` is declared in the partial class - **even when no declared or dynamic property with a similar...