Specify Timezone for Relative Date Filter
I would love to utilize the Relative Date filter to handle things like current month, current year etc. However, when published up to the service, the relative date filter utilizes UTC timezone, and there's no way to account for this currently.
Please allow the ability to specify a timezone to be used by relative date filters, whether it be a tenant wide Power BI Admin setting, or something you can specify in the individual report level.
Sanjeev Patel commented
I have end up with this solution and it works for me at any given time
UTC_Date = IF(DATEDIFF(NOW(), UTCNOW(), DAY) = -1, MyDate - 1, MyDate)
I must be missing something. I can't understand how this has been a problem for years with no solution. Is it really possible that everybody's reports using relative date of today, or any Today() or Now() has never worked properly unless they reside in UTC time zone?
Is this issue really 2 years old??? Is there any way to find out if this is even being considered? It is so simple, yet so frustrating to those in time zones prior to UTC.
Come on Power Bi team...such a basic thing. Such a pain to have to always create custom formulas to get around this issue.
Lindsey Abot commented
I'm currently based in Australia, can someone share their workaround solution to utilise Relative Date filter please?
I'll recommend feature.
Nicolas Nouchi commented
This is something that would be extremely useful in my case, cannot utilize relative date filtering
astonished this is still an issue.
Please, vote up for this idea.!
Jacques Mostert commented
Please vote here as well to get relative date filtering to use local date/time.
Please fix this ASAP Microsoft. We don't all live in America you know.
This causes quite some frustration in my company; being based in NZ, our local time is UTC +12/+13, meaning we have to wait till midday or 1pm of the following day for reports to switch over to the correct date range when using relative date filters. I'm sure it's not much of an issue for those within UTC +/- about 6, but for those on the other side of the world it is quite annoying.
This renders the relative date filter next to useless for daily reports, and adds frustration for other ranges.
Yes please. This is destroying our company's confidence in this product, Such a simple concept as "yesterday" completely mishandled.
Doug MacWilliams commented
Yes, we would like to see this feature enabled also
This is a real issue for our company as well and it is an issue that can only be resolved by Microsoft. The only solutions/workarounds that are possible will either avoid using relative dates all together or will only fix the issue for a particular relative time frame.
The largest similar Idea (most votes) that I have found is below, be sure to vote it up and raise an issue through your support contract.
Matt B commented
Great Idea. Everyone from Australia and all other places far from UTC have spent too long creating additional local time columns in our data tables. This must be a nightmare for people developing reports for readers across different time zones.
I think having two options will solve this problem:
1. Set a "Report Time Zone" (This could be UTC as a default)
2. Each reader can view the report in their own local time according to their settings (obviously report refreshes etc will always happen at the set times)