Issues with importing time in database

I am trying to bulk import opening and closing times into the database through a CSV and for some reason the date/time that shows up in the database is 5 hours behind the actual time in the CSV file.

For example if the date/time in the CSV is Jan 1, 2020 11:00 AM, once I upload the CSV to the database the date/time that shows up in the database is Jan 1, 2020 6:00 AM.

Or if the date/time is Jan 1, 2020 11:00 PM in the CSV, the date/time that shows up in the database is Jan 1, 2020 6:00 PM.

See screenshots below.



If anyone has any ideas as to what could be going on please let me know.


Were the csv dates created by someone else in a different time zone? If so, that is probably the answer (I ran into this recently).
My workaround was to hard code change my mac (not sure if this is possible on a pc) to the same time zone as the csv originator, do the upload and then change back. The alternative would be to convert the dates in the csv to the correct time zone’s time before uploading.

Yes you were right it definitely is a timezone thing. So it looks like Bubble’s server timezone is UTC and mine is EST (GMT-4) which is why I’m seeing the 5 hour time difference.

Since my use case only requires me to extract the actual time value (irrespective of the timezone) I was able to work around the issue by just adjusting my times in the CSV to account for the timezone difference before uploading.

So… I’m having some time trouble…
Are you saying that Bubble saves the time as UTC. Then displays it based on my local time zone?

I have a Date/Time Picker… when I send that date/time value to Zoom I’m off by 4 hours… So I think you’re on to something…

This topic was automatically closed after 70 days. New replies are no longer allowed.