Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Its been brought to my attention that the indicated date range on a relative date slicer is not what is being returned in the date table. The screenshot below shows the anomaly.
This only appears when using relative months. If I set a relative day, week or year the correct date range is returned.
I found this reference from the documentation and I'm wondering if this has something to do with it.
Solved! Go to Solution.
Hi @Anonymous
As you saw in offical document , it depends on the time in UTC . Unless you are in the UTC time zone, you and your colleague must account for the time offset you experience. Of course, you can also implement it through DAX EOMONTH(), returning the data of the previous 6 months .
Best Regards,
Community Support Team _ Ailsa Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Anonymous
As you saw in offical document , it depends on the time in UTC . Unless you are in the UTC time zone, you and your colleague must account for the time offset you experience. Of course, you can also implement it through DAX EOMONTH(), returning the data of the previous 6 months .
Best Regards,
Community Support Team _ Ailsa Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
@Anonymous ,
you have applied relative filter for last 6 six months, that could be the problem.
Thanks,
Arul