Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
The timeline slicer in PowerBI is is filtering on UTC on both the desktop and online server. As I am based in Australia, this is a huge issue as UTC is currently 11 hours behind. This means that the timeline slicer does not show the current date until 11am, essentially meaning that any report with a timeline slicer is behind by a day for the first 11 hours of the day.
This is also an issue when creating calculated columns/measures that use the formula =today() or =now(). These return the local system times when used in the Desktop version, but return UTC when the report is uploaded to the server.
I know that there are workaround solutions for this issue including converting the imported data's datetime to UTC or only importing the data I wish to use and just displaying that data, but this is frustrating to do for every report, and defeats the purpose of including the timeline slicer as a filter option in PowerBI. It also doesn't offer the flexibility and simplicity that PowerBI should be able to offer to the end user.
Can you provide an option to either change the timezone that the server uses at a global/report level (to account for people who work in different time zones), or simply apply the timezone that is used when creating the report?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.