Hi @di.hoang,
yes, we operate across many different timezones, and will always report based on the local timezone.
So for example, we currently have our Org Timezone set GMT+10 (Sydney AEST, though we’re currently in AEDT). The date here is currently 17th December 2021
Therefore if I run a report to show me the performance for the previous day (16th) with {{yesterday}}, I get the correct data.
However for my colleagues in the USA, it’s still the 16th, so if they ran {{yesterday}} , they will get actually get the ‘current’ date, and will see incomplete data. Instead, they would want {{yesterday}} to resolve to 15th, as that’s {{yesterday}} for them.
I see from your documentation that you to plan ‘dashboard level’ overrides
I’d happy to help test this when you’re ready - though would still say controlling this at a dataset level would be better (at least in our situation), as otherwise you can’t have multiple business units on a single dashboard.
Our current workaround to this will be to have a calendar table per-data source, which will contain a ‘isLatestDate’ flag, and filter on that flag.