Hi all,
I’m running into a timezone issue that I suspect other Tadabase users have also faced.
-
My application stores task dates in the database (Date fields, sometimes with a separate Time field).
-
Tadabase’s built-in filters like “is today” or “is before today” are evaluated based on the application’s default timezone (set in App Settings).
-
For example, I’m in Melbourne (UTC+10/UTC+11). Tasks set for “today” don’t appear on dashboards until around 10–11 am local time if the default is UTC, and if I set the default to Melbourne, users in other timezones will see mismatches.
I’ve seen the Tadabase guide on converting DateTime fields to a user’s timezone, which works for display purposes.
What it doesn’t solve
-
Date-only fields are not shifted; they are just calendar days tied to the chosen default timezone’s midnight. That’s why I get the “today’s records appears at 10am” (or equivalent offset) issue when the default doesn’t match the user.
-
Tadabase’s built-in filters (“is today,” “is before today”) are evaluated on that raw value, not on the display-adjusted version.
-
So even if you set up timezone display rules for fields, the filtering logic still happens according to the app’s default timezone.
I’m exploring options like:
-
Adding a separate “Local Date” field that’s populated in pipes when the record is created, using the user’s timezone.
-
Using formula fields or offsets to calculate a local equivalent of “today.”
-
Or relying on frontend scripts to adjust what users see.
Before I go too far down one path, I’d love to know:
How have other builders managed this problem in production apps?
Have you found a reliable way to make Tadabase’s “is today” filters line up with your users’ local day (especially across multiple timezones)?
Thanks in advance for any tips or best practices!