Forum Discussion
Relative Date Filter behaving oddly
Anonymous most likey it is UTC time zone and tha'ts why it changed.
Hi Anonymous
The following limitations and considerations currently apply to the relative date range slicer and filter.
-
Data models in Power BI don't include time zone info. The models can store times, but there's no indication of the time zone they're in.
-
The slicer and filter are always based on the time in UTC. If you set up a filter in a report and send it to a colleague in a different time zone, you'll both see the same data. Unless you are in the UTC time zone, you and your colleague must account for the time offset you’ll experience.
-
You can convert data captured in a local time zone to UTC using the Query Editor.
You might refer to this articles for more reference about the timeset in power bi and the proper solution:
https://radacad.com/solving-dax-time-zone-issue-in-power-bi
-
Community SupportHi Anonymous
The following limitations and considerations currently apply to the relative date range slicer and filter.
-
Data models in Power BI don't include time zone info. The models can store times, but there's no indication of the time zone they're in.
-
The slicer and filter are always based on the time in UTC. If you set up a filter in a report and send it to a colleague in a different time zone, you'll both see the same data. Unless you are in the UTC time zone, you and your colleague must account for the time offset you’ll experience.
-
You can convert data captured in a local time zone to UTC using the Query Editor.
You might refer to this articles for more reference about the timeset in power bi and the proper solution:
https://radacad.com/solving-dax-time-zone-issue-in-power-bi