Hi everyone
I created a new glide big table. I have imported data into it via CSV.
The data contains a phone call log.
After the import I discovered that for date/time columns, glide automatically reduces 3 hours from the date and time value…
(Note: I unchecked the “respect time zone” we dont need it.)
So for example, in the CSV I have a date time of:
8/7/2024 19:01
glide big table shows it as:
8/7/2024 16:01
More over - On the layout view it shows it as 8/7/2024 23:01
When I switch the column type to text, the string shows the correct date and time… which is - 8/7/2024 19:01
So in total I have the date time showing in 3 different offsets…
Very confusing…
Does anyone know if that is a bug or a normal behavior?
When you import the CSV, Glide is applying your UTC offset to the date/time values.
What you need to do is reformat them as ISO8601 date/time strings with UTC offset included, like so:
2024-07-08T19:01:00+03:00
If you do that, they should import correctly.
2 Likes
Thanks Darren
Same goes for adding a row to a table via “Make”?
What do you mean by “your UTC offset”? is that dependent on the device I’m working on when importing?
Whats the best practice to a fail safe process where my data contains multiple timezones and also my staff works from multiple timezones?
Thanks 
Your UTC offset is determined by where you are physically located in the world. Yours appears to be UTC+3, which means you are 3 hours ahead of Greenwich Mean Time.
No, adding a row is fine. You can use the now value from Make. Just ensure that Make is configured to use the correct time zone.
Are you still talking here about importing via CSV, or adding rows via the App? You don’t have to do anything special when rows are added via the App, but if you have users in different timezones then you should have the “Respect time zone” option checked.
2 Likes
Our users dont add data to the system, the data comes from external sources and is for view only.
On a day to day basis it will come into the system via Make however
the nature of our process is that every once in a while we have to do a bulk upload of data via import, because of various data integrity reasons…
We prefer not to use the “Respect time zone”, we want to avoid confusion. there are account managers that are traveling all the time and we prefer them to see the absolute time and not the relative one…
We are working with bigquery as our DW but had to move to Glide big tables because of performance issues with Glide app…
Managing the data with BQ is easier, now that we moved to Glide big tables I need to find all sorts of workarounds for how to handle data integrity issues and bulk uploads…
Thanks for your help!