So in the date/time column which is respecting timezones and on medium, it is showing the time as 9/9/2024, 12:07:10 PM
However, when I format the date using the format date column and the formatting “tt” it returns 10:07:20 AM. How do I fix this or just add 2 hours to the time?
What do you mean by “format the date using tt”? Do you mean using the Format Date column?
Correct sorry, format date column and tt is the formatting used.
I guess it’s the underlying value that’s at fault here. If you disable respecting timezones, does it still return 10:07:20 AM?
Hi, so it shows it fine in the column itself:
But when bringing it through with the Single Value and then trying to format it it ends up like so: (3:19 changing to 13:19/1:19)
On the original table, if you add a JavaScript column and use “return p1”, with p1 being the datetime column, does it show 13:19 as well?
If you remove the “respect timezone” checkbox, does it show 3PM or not?
Whether we have it as respect timezones or not, it shows 5:19 here and 3:19 in the other columns. I have changed it back and forth 4 times. Does not change anything.
Is there no way to just add 2 hours to a date if this isn’t working?
Yeah you can just use a math column to do it, e.g: T + 2/24, but it does not solve the original bug.
Should I go report it as a bug and call it there? I can play around a bit more in the meantime.
Yeah, I think you should report a bug, though that Format Date column has been known to be troublesome for a long time.
The problem with just blindly adding 2 hours is that it may look good to you, assuming you are currently 2 hours away from UTC time, but someone in another timezone is now still off by an hour or more, minus that 2 hours.
When ‘Respect Timezone’ is turned on, I believe Glide stores UTC time behind the scenes, and adjusts the time you see to your local timezone. When it’s off, it normally always assumes the the time is local time, regardless of timezone.
Like @ThinhDinh said, it feels like a bug and probably a long existing one at that. I don’t feel date handling in Glide has ever been fully polished, especially when using computed date columns. Even ‘Respect Timezone’ seems finicky, but I’ve never had to use it, or deal with it.
If you still wanted to work around it, you would have to first figure out the UTC offset for the signed in user first, then take that offset number and add the difference to your date. It’s a doable workaround if needed, but would be better if Glide addressed it properly.
All our customers are based in one country thankfully, including all users etc. I do agree though, still needs to be addressed.
