Relative date filter returns wrong date range

[bMan]

Hi all.

I'm pretty new to Power BI, but I've spent a decent amount of time in Excel and Power Query. I've "inherited" and customized a time allocation tool for work, based on input in Excel sheets, pulling the data into PBI using PQ and outputting a report that is shared on Teams. People estimate time spent on various projects over the next weeks. Using a relative date filter, users can filter data in the report to the next N weeks or months. This all works perfectly for most people (a little over 200 users). However, a few users get the wrong period returned from the date filter. All users are in the same time zone and everyone is opening the report from their respective Teams group, shared from a PBI workspace. The dates come from a lookup table relating week numbers (used in the input sheet) to a date in that week.

The returned period is off by months, which leads me to believe this is not a locale- or regional settings-related issue, but I don't know. Most suggested solutions, both from google-ing and "copilot-ing" seem to point in this direction. Strange thing (maybe) is I get the same error in my desktop app, but not in the published report. Any hints towards a solution would be greatly appreciated.

[v-pagayam-msft]

Hi @bMan ,

Could you please confirm whether you have resolved issue or found the solution. If yes, you are welcome to share your answer and mark it as a solution so that other users can benefit as well. This will be helpful for other community members who have similar problems to solve it faster. 

If we don’t hear back, we’ll go ahead and close this thread.Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.
Thank you.

[bMan]

I answered this back in march, saying that the workaround I found didn't qualify as a solution, and that I didn't have more time to work on it. That is still the case, so you can close the thread. 

Thanks.

[v-pagayam-msft]

Hi @bMan ,
As we have not received a response from you yet, I would like to confirm whether you have successfully resolved the issue or if you require further assistance.If it solved, please consider accept it as solution.

Thank you for your cooperation. Have a great day.

[bMan · Accepted solution]

Hi.

Sorry for not following up on this. I have been busy with other tasks. I finally had time to look into this again on friday, and I don't think locale settings is the cause. I tried changing the "Locale for import" from "English" to local and back, and I also tried switching the "DAX separators" back and forth. My relative date filter is stuck on the same start date. Meanwhile calculations using "today()" work fine.

For now I don't have more time to spend on this. I've "solved" this problem by switching my relative date filter to "between", and I'll keep that until people complain about it.

Thanks for your suggestions!

[v-pagayam-msft]

Hi @bMan ,
Thank you for sharing the solution with us. Glad it resolved your query, please mark your answer as "Accept as Solution" to help others find it more easily.

Thank you for your cooperation. Have a great day.

[bMan]

I don't really consider this a solution. It's a workaround, and it gets the job done in my case, but I'd rather let it remain "unsolved" until a solution for the actual problem is found.

[v-pagayam-msft]

Hi @bMan ,
We wanted to follow up since we haven't heard back from you regarding our last response. We hope your issue has been resolved.
If my answer resolved your query, please mark it as "Accept as Solution" and select "Yes" if it was helpful.
If you need any further assistance, feel free to reach out.
Thank you for being a valued member of the Microsoft Fabric Community Forum!

[v-pagayam-msft]

Hi @bMan ,
May I ask if you have gotten this issue resolved?
If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.

Thank you for your cooperation. Have a great day.

[v-pagayam-msft]

Hi @bMan ,
Thank you for reaching out to the Microsoft Fabric Community Forum about the issue you are encountering.
Thank you @zenisekd for the prompt response.
Upon reviewing , providing the insights which might assist you in resolving the issue.

1.In Excel, if dates entered as text, Power BI might not interpret them correctly because of differences in regional settings.

2.In Power BI Desktop, follow these steps:

Go to File > Options and Settings > Options.

Under Regional Settings, set the locale to match your date format. This helps Power BI understand your dates correctly.

If this post helps, please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

[zenisekd]

Hi @bMan , any chance, that this could be caused by the locale format used? Such as that instead of 1.2.2025 (Feb 1 2025) it would do the date in the format 2.1.2025 (Jan 1 2025)?