ISSUE:
Suppose you are on EST time and all data is ingested according to your local timezone, so in EST time for this example. The issue remains the same for other timezones. So, when a report page is supposed to show data from yesterday only, so one day back only, and thus nothing from today or the current day, the semantics of 'yesterday' means the current day of the month - 1 starting at 00:00:00 until 23:59:59.999, and not from 00:00:00 until 19:59:59.999. As things stand today, the slicer selected date will jump to the next day at 7 or 8 PM depending on whether or not DST is active. So in the screenshot below, when local time in EST reaches 8 PM, the selected date in the slicer jumps to 5/22/2025! But locally, the day is not over yet and the slicer stops showing yesterday's date. Not great.
PLEASE FIX THIS. IT HAS BEEN 10 YEARS OR MORE THAT THE BURDEN OF CREATING A COMPLICATED AND CUMBERSOME WORKAROUND HAS BEEN PUT AND LEFT ON THE SHOULDERS OF THE USERS WORDLWIDE THAT, TO ADD INSULT TO INJURY, CANNOT EVEN DEAL AUTOMATICALLY WITH DST CHANGES.
As if we are not already too busy trying to do the main work we are hired to do, rather than fixing stuff that doesn't work in our main tool.
One would expect this kind of feature to be gracefully handled automatically and out of the box by software like Power BI Desktop, which does have a lot more complicated features already baked in, like Time Intelligence, for example. So why not auto handling of timezones???
SOLUTION:
In the format pane, implement a timezone toggle for all the various visuals that work with date, time, or datetime types. 1 toggle button to put the visual in UTC or local timezone mode. Done! How easy is that, right?
Shouldn't take 10 years and counting to get such a feature.
... View more