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!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hey! I'm new here but was hoping to have a question answered. Before Decemember Now() was being used to show when the Last Refresh for the data happened in Power BI. It's very simple:
When the data refreshed this would update to say when that data refreshed happened. It's like in sql where you can show the current date with a function, but only when you hit the execute button, so it only shows when it was last executed. However, after December we have noticed that Now() datetime is always updating in our app. If someone refreshes the webpage it is showing the current date and time and counts up each second for each refresh for the time that they accessed the webpage. It's always updating, not just on data refresh. Is there a setting we need to change to stop this behavior and have it go back to the previous behavior?
Thanks!
Solved! Go to Solution.
I would recommend you to create a new dataset with an expression
= DateTime.LocalNow()
Make sure to convert the dataset into a table and change the format accordingly. The datetime will only be changed after the dataset are refreshed.
Proud to be a Super User! | |
The DAX function NOW() is expected to change whenever it is called (although the value may be cached in some cases), not just at data refresh. So the current behavior is the intended behavior and I'm not sure what sort of caching was happening before.
@Kaviraj11's suggestion is good. Defining the timestamp as a table in the query editor works well since queries are only refreshed when the data is refreshed. Anything upstream from the query editor should also work.
Will I need to worry about this behavior changing in the future? It just seems more stable to do this through SQL if how these things work change like this. Especially if there's no way to salvage this and will need to go across 100 reports to update all of these anyways.
No, you don't need to worry at all.
You can give it a try and if it doesn't work, you can always use it through SQL.
Proud to be a Super User! | |
I would recommend you to create a new dataset with an expression
= DateTime.LocalNow()
Make sure to convert the dataset into a table and change the format accordingly. The datetime will only be changed after the dataset are refreshed.
Proud to be a Super User! | |
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Power BI update to learn about new features.
User | Count |
---|---|
9 | |
8 | |
7 | |
4 | |
3 |
User | Count |
---|---|
14 | |
13 | |
11 | |
10 | |
10 |