Date filter is not region aware and "last calendar month" is therefore not working on 1st new month

[MikeDS]

Date filter is not region aware and "last calendar month" is therefore not working on the 1st of a new month before 10am in Australia. At 10am it is UTC+0 and suddenly the filter will work but users are frustrated until 10am on the 1st of a new month.

To be clearer, it was 8am, 1st Dec this morning and "Last Calendar Month" showed October instead of November. At 10am, November showed as "Last Cal Month" as it should.

[v-lili6-msft]

hi  @MikeDS 

This is designed by default

Limitations and considerations

The following limitations and considerations currently apply to the relative date range slicer and filter.

• The data type for the field in the slicer must be a date, and not the default of text. Otherwise, the relative options don't show up in the slicer.
• 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 both see the same data. Unless you are in the UTC time zone, you and your colleague must account for the time offset you experience.
• You can convert data captured in a local time zone to UTC using the Query Editor.

https://docs.microsoft.com/en-us/power-bi/visuals/desktop-slicer-filter-date-range#limitations-and-c...

and here is the idea for this:

https://ideas.powerbi.com/ideas/idea/?ideaid=769707bf-a6ab-4ed1-81e2-ff0608c87d7e

for your case, you need to adjust it with your local time zone. 

here are the blog, please refer to

https://radacad.com/relative-date-slicer-for-your-local-time-zone-in-power-bi

https://whitepages.unlimitedviz.com/2020/05/working-with-time-zones-in-the-power-bi-relative-time-sl...

Regards,

Lin

[MikeDS]

Ok, thanks for that. Voted up those links.