HI, @benjaminhoang
This is due to UTC time in your report.
Relative date range filter is currently by design as it’s always based on UTC time
The following limitations and considerations currently apply to the relative date range slicer and filter.
- Data models in Power BI do not include time zone information. 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, so if you configure a filter in a report and send it to a colleague in a different time zone, you'll both see the same data. However, if you aren't in the UTC time zone, you might see data for a different time offset than you expect.
- Data captured in a local time zone can be converted to UTC using the Query Editor.
Different timezone support is definately required, even if its simply takes the timezone of the local user. Users generally expect that "Today" is the today of whereever they are.
In our cases, we often set head of time what Today means as our reports span multiple timezones. It is important for us to make sure that the Today of the report aligns with the Today of the data import. There will come a point in our future where we will have data imported for all corners of the globe and using Today by UTC is problematic.
here is the same post for you refer to
https://community.powerbi.com/t5/Issues/Relative-Date-Filtering-is-offset-even-in-Power-BI-Desktop/i...
https://docs.microsoft.com/en-us/power-bi/visuals/desktop-slicer-filter-date-range
Best Regards,
Lin
Community Support Team _ Lin
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
