Jan 12, 2019 11:57 AM
Hello! I have a lookup field in one table to copy over a date from the connected record. This has been working fine, except for one entry that for some reason is displaying the lookup date as the day after the actual date from the connected record. Any thoughts on why this might be happening?
Thanks so much!
Jan 13, 2019 09:08 AM
‘Off by a day’ errors in date files is almost always caused by the ‘Use UMT’ toggle being set (or not being set, depending). Even if you don’t have ‘include a timestamp’ toggled, the GMT switch may be flipped. First step, check that.
Two things to keep in mind, though:
1/1/2019 8:00am
, and you toggle on ‘use UMT,’ the display doesn’t change to show what 1/1/2019 8:00am
in your local time would be in UMT; instead, the field value is shifted forward or backward the number of hours your timezone is offset from UMT.¹For example, I’m on Pacific Standard Time, which is -0800 (8 hours behind) UMT. If I define two fields, {Date}
and {DateF}
, where {Date}
is a date field and {DateF}
is a formula field set to equal the value of {Date}
, here’s what I get with different combinations of settings:
UMT on | Date | DateF |
---|---|---|
neither | 1/13/2019 7:30am | 1/13/2019 7:30am |
Date | 1/13/2019 7:30am | 1/12/2019 11:30pm |
Date, DateF | 1/13/2019 7:30am | 1/13/2019 7:30am |
DateF | 1/13/2019 7:30am | 1/13/2019 3:30pm |
SET_TIMEZONE()
function allows you to force a standard timezone for all your dates.²Jan 17, 2019 09:20 AM
Thank you so much! That was definitely the problem. I appreciate your help, and now I know how I need to set up my datetime fields in the future!