Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
MeirStroh
Frequent Visitor

Include today in date slicer not working in app

Hi 

 

I'm not sure in which forum to put this cause it's an issue i'm having in the app 

 

When i change the include today (see photo below) for a date slicer it works well in the desktop but when i publish my workspace to an app it doesn't work there but in the workspace it does work is this a known thing that the app just doesn't support it yet?

 

MeirStroh_0-1746566752985.png

just want some clarification thanks in advance,

Meir

 

 

2 ACCEPTED SOLUTIONS
V-yubandi-msft
Community Support
Community Support

Hi @MeirStroh ,

Thank you for engaging with the Microsoft Fabric Community. In additon to @vicky_ response.

This is expected behavior in the service and not a bug. The slicer evaluates  today based on UTC, which may lag behind your local time zone by several hours (IST is UTC+5:30).

You can adjust the current time by adding or subtracting hours using DAX expressions. To determine the local time zone, you can utilize Power Query functions or retrieve the time zone dynamically using a Web API query.

 

Helpful Reference:

Solved: Include Today not working in Relative Date - Microsoft Fabric Community

 

Did I answer your question? Mark my post as a solution.

View solution in original post

You're right that the date being evaluated in UTC can cause a few hours’ difference depending on your local time zone — that part is expected. However, in my case, that wasn’t the main issue.

What I discovered is that updating the app alone doesn’t always apply certain changes, like tweaks to slicer settings or “Include Today” toggles. Even though I had saved and republished the report multiple times, the app seemed to hold on to an older cached state.

To resolve it, I removed the report from the app and then re-added it — and suddenly the slicer worked as expected. So while the UTC explanation is technically correct in my case it would only make a few hour difference, there seems to be a deeper issue where some minor report-level updates don’t fully apply in the app unless you rebind the report.

Definitely strange behavior, but worth keeping in mind for others running into the same thing.

View solution in original post

6 REPLIES 6
V-yubandi-msft
Community Support
Community Support

Hi @MeirStroh ,

Has your issue been resolved, or do you require any further information? Your feedback is valuable to us. If the solution was effective, please mark it as 'Accepted Solution' to assist other community members experiencing the same issue.

V-yubandi-msft
Community Support
Community Support

Hi @MeirStroh ,

Could you let us know if your issue has been resolved or if you are still experiencing difficulties? Your feedback is valuable to the community and can help others facing similar problems.

 

Thank You.

V-yubandi-msft
Community Support
Community Support

Hi @MeirStroh ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank You.

V-yubandi-msft
Community Support
Community Support

Hi @MeirStroh ,

Thank you for engaging with the Microsoft Fabric Community. In additon to @vicky_ response.

This is expected behavior in the service and not a bug. The slicer evaluates  today based on UTC, which may lag behind your local time zone by several hours (IST is UTC+5:30).

You can adjust the current time by adding or subtracting hours using DAX expressions. To determine the local time zone, you can utilize Power Query functions or retrieve the time zone dynamically using a Web API query.

 

Helpful Reference:

Solved: Include Today not working in Relative Date - Microsoft Fabric Community

 

Did I answer your question? Mark my post as a solution.

You're right that the date being evaluated in UTC can cause a few hours’ difference depending on your local time zone — that part is expected. However, in my case, that wasn’t the main issue.

What I discovered is that updating the app alone doesn’t always apply certain changes, like tweaks to slicer settings or “Include Today” toggles. Even though I had saved and republished the report multiple times, the app seemed to hold on to an older cached state.

To resolve it, I removed the report from the app and then re-added it — and suddenly the slicer worked as expected. So while the UTC explanation is technically correct in my case it would only make a few hour difference, there seems to be a deeper issue where some minor report-level updates don’t fully apply in the app unless you rebind the report.

Definitely strange behavior, but worth keeping in mind for others running into the same thing.

vicky_
Super User
Super User

It's kiiiinda on purpose. All the times on powerBI service are based on UTC times, so the "today" that you're seeing is the UTC today which is likely different from your time zone. 
There's a couple of ways to deal with it:

- don't look at the report until UTC date is the same as your date (not practical)

- change your dax / code to have an offset - there's some threads floating around on how to do this e.g. https://community.fabric.microsoft.com/t5/Desktop/Power-BI-is-automatically-converting-UTC-time-to-l... and https://community.fabric.microsoft.com/t5/Service/Power-BI-service-showing-UTC-date-despite-local-ti...

 

Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

Find out what's new and trending in the Fabric community.

July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.