Current filter:
                                You should refresh the page.
                                  • Hello,

                                    I'm experiencing different behaviour when rendering datetimes in Devextreme form. The form model has two datetime fields. One is type of DateTime and the other is type of Nullable<DateTime> aka DateTime?. Both of them are served with 'Kind' property set to Utc.

                                    The rendered JSON form data look like this:

                                    "RegisteredAt":new Date(2019, 1, 12, 14, 53, 59, 360),"ExpiresAt":"2019-02-12T14:54:59.36Z",

                                    The 'RegisteredAt' field is type of DateTime and is rendered as new Date(....). The problem with this one is that it is not transformed to client's time zone.

                                    The 'ExpiresAt' field is type of DateTime? and is rendered as UTC ISO string. This one is correctly transformed to client's time zone.

                                    So the Nullable<DateTime> behaves correctly from my point of view. The non nullable one produces unexpected result.
                                • Nikolai (DevExpress Support) 02.13.2019

                                  Thank you for bringing this to our attention. We've reproduced the issue and need additional time to research it. We will update the ticket when we have any news.

                                1 Solution

                                Creation Date Importance Sort by


                                • 18.2.7 : Hotfix requested and is being prepared
                                • 18.1.10 :