Odata DateTime TimeZone issue on PUT method after migration from .net4.7 to .net6

[MADzO]

The whole explanation can be found here: https://stackoverflow.com/questions/71342051/odata-datetime-timezone-issue-on-put-method-after-migration-from-net4-7-to-net

[julealgon]

@MADzO Please check if your route is being detected as an OData route. Enable the route debugging middleware and navigate to /$odata. Post the results here.

[MADzO]

It is part of the OData Endpoint Mappings

[julealgon]

@MADzO can you confirm which of those endpoints is the one you are targeting with the request?

[MADzO]

Yeah sure.
It is visible also on the picture on stackoverflow.

[julealgon]

I wonder if this is somehow related to this:

• Time zone settings not propagated to query #384

[xuzhg]

@MADzO Basically, i didn't fully understand your scenario. I created a sample at https://github.com/xuzhg/WebApiSample/tree/main/v8.x/TimeZoneSamples, can you make it failing or we can set up a meeting to sync it?

[MADzO]

@xuzhg just send me a teams meeting and I can explain in detail. In meanwhile what you can see from the pictures is that same request with same data received in the old net4.7 and in the new .net6 solutions, has different values for the properties of type DateTime in the odata controller. Just check the values in the watch on the second picture in the very bottom and you will see it.

[xuzhg]

Sent in email

[MADzO]

First of all @xuzhg thanks for the help and flexibility. Really apricate it.
Secondly we did conclude that if you do not have [FromBody] attribute in front of your complex parameter in POST/PUT method, OData will not even consider it as Odata parameter. That means that Odata serializer/deserializer will not be runed at all.
Also have it in the mind that OData works only with application/json content type.

[julealgon]

Secondly we did conclude that if you do not have [FromBody] attribute in front of your complex parameter in POST/PUT method, OData will not even consider it as Odata parameter. That means that Odata serializer/deserializer will not be runed at all.

@MADzO consider annotating your controller or assembly with the [ApiController] attribute. This changes a few inference rules in the framework, including "treating complex types as [FromBody] by default". It is a very useful attribute for pure API projects.