Most of our users are in Pacific Standard Time zone, however, our data are stored in UTC format. Because by default there’s no support for timestamps, we’re sending only dates to GoodData. But this causes some dates are displayed differently in GoodData and in the main application. For example Apr 21, 2023 - 6:13pm Pacific time displayed in the app is already 22/04/2023 in GoodData (as it’s UTC).
One solution I see is to normalize dates from UTC to timezone that should be used in a given workspace for data upload. That would work well if all workspace users were in the same time zone.
Would there be any good solution that could work for a workspace that can be used by users in different time zones? So they could see base date displayed in their desired zone? I don’t see how custom time dimension could help here, as if I understand it correctly, it’s rather for proper data filtering and segmentation and not for dynamically formatting dates.
Best answer by Julius KosView original