Different date information on the form archive and in the follow up form

[marinam]

Hi @eddy.daouk,
I’m contacting you again because of the similar issue.
We have the problem how date/time is presented in different time zones again.
We didn’t implement your suggestion from the article above.
My colleague has user settings Arizona, the date and time (both data elements have TimeZone Arizona) he sees in the follow up form is correct, but when he opens request, he sees one day before (please see screenshots). Is there any other setup that has to be updated in order for this to work? Our company works in two time zones - GMT+1 (Belgrade), and GMT-7 (Arizona).
I found this article, it explains similar issue like we have:

How can I set a datetime value for form data in code-behind with the consideration of user time zone and Daylight Saving time?

Background WorkflowGen will automatically take the date value entered by user from a DateTime text field on a web form and add the proper value to the FormData. However, if a date is set manually in code-behind, by default the date will not have the time zone factor and it will cause a date issue. For example, May 1, 2019 (2019-05-01) will become 2019-05-01T00:00:00 in the WorkflowGen form data. When this value is passed to WorkflowGen process data, if the time zone is Eastern US & Canada time,…

Could this maybe resolve the problem?
Could you please help us to resolve this issue?
Thank you!
Marina