DevExtreme v23.1 is now available.

Explore our newest features/capabilities and share your thoughts with us.


This section describes common issues related to data binding and gives recommendations that help you resolve them.

Date values are parsed or serialized incorrectly

Issue: Date values have an unexpected format when they are displayed in the component or sent to the server.

Different browsers parse date strings differently. To compensate for this inconsistency, DevExtreme components use an internal parser. The latter only supports date strings that comply with the ISO 8601 standard, that is - strings that have the following formats:

  • "yyyy-MM-dd" - parsed as a local date

  • "yyyy-MM-ddTHH:mm:ss" - parsed as local date and time

  • "yyyy-MM-ddTHH:mm:ssZ" - parsed as UTC date and time

  • "yyyy-MM-ddTHH:mm:ssx" - parsed as date and time with a timezone

Date strings in other formats are passed to the Date constructor. There are times when this approach produces different results. Refer to the Date.parse() article for more information. We encourage you to use the ISO 8601 formats to guarantee the absence of possible issues.

If your date strings conform to ISO 8601, DevExtreme components can automatically detect their format and use it for date serialization. However, the detection does not work if the data source is empty. In this instance, set the dateSerializationFormat property to specify which ISO 8601 format should be used. This property is supported by all components that allow users to edit date values: