Why is DateTime Localize missing the time zone after retrieve in a scheduled event?

0
Hello Mendix Community,   A persistent DateTime Localize field has a time zone (+0100) before commit and is missing the time zone (+0000)  after retrieving it in a flow started with the scheduled event.   In the application settings, under Runtime, the default time zone is GMT+01:00 Amsterdam and the time zone of the scheduled event is also GMT+01:00 Amsterdam.   When we use the format formatDateTime($WorkflowContext/Mutatiedatum, 'HH:mm:ss') is UTC time and not Local Amsterdam +1 as expected.   Are we missing a configuration somewhere? Or are we doing something wrong?   Kind regards, Pascal
asked
4 answers
0

Hi Pascal, 

 

Please read the first paragraph of this FAQ :-) It will probably provide all the answers you need ... 

 

Goodluck!

answered
0

Is localized set to true or false for this attribute? Because if it is false it will always show UTC. Do note that no matter how this boolean is set the date will always be UTC in the database. But if localized is set to true it will display the value in the timezone of the user.

Regards,

Ronald

 

answered
0

image.png

Element Mutatiedatum is set to Localize = True.

 

Before commit, see +0100, local time 14:36 is true

image.png

 

After retrieve, see +0000, local time 13:36 is false, this is the UTC time

image.png

 

 

answered
0

Scheduled events make use of the server time, probably UTC. We are experiencing the same problem.

answered