Using {now} formula in massupdate returns wrong date/time zone

Hi All,

We would like to use the Mass Update function to update a customized Date/Time field. When using formula {now} the field is set to the wrong time zone approximately 9 hrs ahead of the current time/user’s time.

Time zone on user preferences are set to GMT+1, The update sets 2022 03 30 19:28 when in reality the time is 10:28

When using formula {now} in a saved search the returned value is correct. Does anybody know how to fix this on a mass update?

Rookie Asked on March 30, 2022 in Saved Searches.
Add Comment
0 Answer(s)

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.
  • This site made possible by our sponsors:   Tipalti   Celigo   Limebox   Become a Sponsor