- Set the “Start Date” field to be in UTC
- I already have a table called “Locations” with the filed “timezone”, so I could add another field called “UTC Offset” (for example Australia/Perth would be “8”).
- Create a new formula field (eg “UTC Date” with a calculation like "if location = Australia/Perth, "Start Date + “UTC Offset”.
In this way, you will end up with dates that resemble the ones users entered in their form but are in a different timezone, resulting in completely different dates in the end.
Unfortunately, a date field requires a single timezone to function properly.
My approach to addressing your request would depend on the specific problem you are trying to solve.
If the issue is sharing an invite at the right date and time, you simply need to input the correct date and time in your date field using the todate_tz formula, as previously discussed.
Here’s a couple of pictures as an example:
As you can see, in my Baserow table, I’m enforcing the Australia/Perth timezone.
However, when I send an invite for that date and time, my calendar will show the event in my system’s timezone, which is Europe/Rome. For simplicity, I used our ability to sync calendars with external calendar apps here, but an integration with N8N should work as well.
If, instead, you’d like to see it in the timezone chosen by the user, then probably a date field is not the correct choice considering how it works.
I’d probably store the data in this way:
- the date in a date field without time
- the time in a single select field if I want to only allow some predefined slots, otherwise a single select field
- the timezone in a single select field containing the available timezones as options.