Change date format in JSON request

[Remo]

We've got a simple model with a property LogDt defined as System.DateTimeOffset.

When we fetch something, the odata server returns the date like this: "2021-06-16T12:12:12Z". This is a behaviour which we cannot change, it's a third party product.

When setting the date in C# (we tried DateTimeOffset.UtcNow, DateTimeOffset.Now, DateTime.Now and more) and then try to submit the PATCH request, the server receives either 2024-11-27T07:54:55.0481881Z or 2024-11-27T08:53:53.8399277+01:00.

Our 3rd party odata server does not seem to like milli-, micro- and nanoseconds.
How can we change the date format in the JSON request when building a request?

• There are some examples when building an odata server, but we are building a client (https://stackoverflow.com/questions/69267820/use-odatapayloadvalueconverter-with-net-5-and-microsoft-aspnetcore-odata-8-0-2)
• I also tried to register a converter for ODataPayloadValueConverter with services.AddSingleton(typeof(ODataPayloadValueConverter), pvc => new DateTimeValueLocaliser());, but this never gets called

[Remo]

A colleague found a few things on this page https://learn.microsoft.com/de-de/odata/odatalib/release-notes/odatalib-8

• services.AddSingleton(new ODataJsonWriterFactory());
• services.AddSingleton(new ODataUtf8JsonWriterFactory(JavaScriptEncoder.Default));

Unfortunately this also didn't seem to have an impact. I also create my own factory, but it never got called.

[Remo]

We found a work-around, instead of using DateTimeOffset.Now , we can use new DateTimeOffset(DateTimeOffset.Now.Ticks/10000000*10000000, DateTimeOffset.Now.Offset). That way the precision that doesn't match property definition, will be truncated. In our case, it was simply because the server defined a precision that was different from what our C# client was sending.