I have created a form to schedule meetings with our company. However, I have noticed that when someone from another time zone picks a time for a meeting using the “Date/time” field, Airtable schedules this meeting in this person’s time zone. For example, if someone in London picks the time 10:00 am, the meeting will be at 10:00 am their time (3:00 am CST). Is there a way to have this “Date/time” field to only stick with Central time no matter where the person is located? For this particular case, the meeting will be 10:00 am CST, not 10:00 am London.
Thank you, @ScottWorld, for your reply. The problem is that, in this case, the meetings will be scheduled in GMT (not CST), correct? This means I must create a formula field to convert the time into CST, right?
Although this will show the same timezone for everyone, I think this is a risky design, especially if you eventually create a calendar integration.
There is no way to change how the Airtable form works. You can add help text to the form to let the users know the form uses local time.
You can also have a separate date field for just the date, and then a text field for entering the time. Then use a formula field to calculate the combined date/time. The formula will be rather complex because it will need to take into account the timezone offset, which can change throughout the year.
Are you just looking at the list of dates & times in Airtable and scheduling things there? If so, then you don’t need to do any conversions, because all times will always be displayed uniformly in Airtable. All time zones will see the times as exactly the same.
However, if you’re sending the times to Google Calendar or another calendar service, then yes, you would need to create a formula field that offsets the time properly so that Google Calendar adds it at the right time. (I believe that Airtable always sends data to other services in GMT, so your offset would need to take that into account.)
I do not think this is risky. I think it is the most efficient & straightforward way of handling this. It just requires a formula field to handle the offset, as I demonstrate in my time zone base & video above.
But yeah, @Mission_Quest, time zones are extremely tricky in Airtable because Airtable doesn’t handle them in the most straightforward way. So even with the guidance above, you’ll likely have to play around with things for a while until you get it exactly right.
Unless you have people choose their time zone from a list (which is another great idea), I don’t think you’ll have any other choice but to leave GMT turned on. Otherwise, the times will all be coming in at a variety of wrong times, which was your original issue.
I would spend some time with my time zone base & time zone video to help you create the formulas.
p.s. Also, if your company is large enough to hire an Airtable consultant, I can work with you on creating all of this with you.
Airtable automatically handles daylight savings time. (Although it does it in a slightly confusing way. It pre-adjusts times in the future based on as if you were looking at it from today’s point of view. It’s odd.)