Why do nanoflows not take into account non-localized date times?
0
Hi there, this is mainly out of curiosity: We have an object on which we save the date of the week in a StartDateUTC field. When creating the week we determine the date and save it at UTC midnight. When we retrieve this object via a microflow from database, this is correct and indeed non-localised UTC field. When use this same object in a nanoflow from memory basically, the dates shown for UTC and localized have been shifted. Specifically, the localised time in the debugger is the non-localised saved time. In order words: datetime saved at midnight UTC with non-localised in domain model is suddenly a localised time when used in a nanoflow. Does anyone know the reason why the nanoflow ignores the non-localised component completely ?
asked
Desiree de Ridder
1 answers
0
Non-localized property of a datetime attribute only affects the presentation in a UI. So, the utc time in the database is always utc, never localised. The sessiontime in the debugger shows utc+sessiontimezone. So what we are seeing is that the retrieve of this non-localized attribute via nanoflow represents the utc wrong when looking at it in the debugger. My guess is that showing this attribute in the UI, shows you the expected non-localized value. If that is so, then we are witnessing strange internal behavior.