I have a kendo grid plugged on a OData service providing date into the Microsoft date format and everything is working like a charm.
However, the OData service will be upgraded to be ISO 8601 compliant. Kendo grid seems to handle it very well.... except for one thing: Milliseconds.
Indeed, even if I set the column format to {0:yyyy-MM-dd HH:mm:ss.fff}, the displayed milliseconds are always set to 0.
Ex:
-With Microsoft date format, the OData value /Date(1376439064929-0400)/ will be displayed as 2013-08-13 13:31:04.929
-With ISO 8601 date format, the OData value 2013-08-13T20:11:04.9297826 will be displayed as 2013-08-13 20:11:04.0
Is it a bug or is this the expected behavior from the Kendo Grid?
Best regards,
Simon
P.S. I know the ISO date format isn't officially supported by OData but Kendo already did most of the job for handle the ISO date format...
However, the OData service will be upgraded to be ISO 8601 compliant. Kendo grid seems to handle it very well.... except for one thing: Milliseconds.
Indeed, even if I set the column format to {0:yyyy-MM-dd HH:mm:ss.fff}, the displayed milliseconds are always set to 0.
Ex:
-With Microsoft date format, the OData value /Date(1376439064929-0400)/ will be displayed as 2013-08-13 13:31:04.929
-With ISO 8601 date format, the OData value 2013-08-13T20:11:04.9297826 will be displayed as 2013-08-13 20:11:04.0
Is it a bug or is this the expected behavior from the Kendo Grid?
Best regards,
Simon
P.S. I know the ISO date format isn't officially supported by OData but Kendo already did most of the job for handle the ISO date format...