When binding a grid to a list of objects that contain a datetimeoffset, there is a newtonsoft exception thrown. Changing it to a DateTime fixes it but we can't always change the source objects and creating a wrapper layer is kinda time-consuming. Is this a bug or should I be doing something before using objects with offsets?
VNVignesh Natarajan Syncfusion Team August 14, 2019 05:24 AM
Greetings from Syncfusion support.
Query: “When binding a grid to a list of objects that contain a datetimeoffset, there is a newtonsoft exception thrown”
We are able to reproduce the reported issue at our end while using Template Columns. Since it is a known issue, we have logged a defect “Script error is thrown with DateTimeOffset property in Grid”. We have fixed the reported issue and fix for the issue will be included in our upcoming Nuget release which is expected to be rolled out on or before 19th August 2019.
You can track the status of the issue and contact us through the below feedback link
Note: There is a break in the @ref functionality in Blazor with Preview 8. If you are accessing our component instance in code behind using @ref, you need to define both @ref and @ref:suppressField in all component’s tag-helper as shown in the below code snippet. Please refer to this GitHub thread for more information.
In this release we have included fix for the issue “Script error is thrown with DateTimeOffset property in Grid”. For your convenience we have prepared a sample in our latest Nuget release which can be downloaded from below