Bug in NullDate saving to local storage


We recently encountered again an issue that when saving null date value from server entity to local storage it is not saved as 1900-01-01 00:00:00 but as 1900-01-01 00:34:45 (minutes part seems to be random) on some devices and browsers. This leads to situation when comparing it ti NullDate() returns false. 

We currently use workaround by converting DateTimeToDate() but this seems like OutSystems bug.

We will appreciate any advice of how to prevent this in future and what can be the nature of the issue.

Thank you

Hi Mykola (Nick) Tkachenko,

Thanks for sharing, this is important to know, and have in mind we need to compare with null date. Did you reported this to OutSystems?

Hi Marco,

I'm not sure what is the best way to share concerns whether this is platform bug or settings issue or something else. So as OutSystems monitors community I assume that they will notice this post and can give some clarifications. Also if it is really a platform bug there should be other developers who had this issue.

It might be related to https://success.outsystems.com/Support/Enterprise_Customers/Maintenance_and_Operations/Behavior_of_the_Null_DateTime_Value_in_Mobile_Apps but as the time added is not hours or some react value it seems like another thing.