Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi,
Can someone explain to me why the timestamp in the Power BI Service is not according to the selected Arizona time zone when it comes to refreshing?
The Refresh timestamp in Power BI after refresh whereas it is really 2:28 PM here in Arizona....
How do I fix this??
Thank you,
Holly
Solved! Go to Solution.
thats is M. Applied step name is automatically generated so DAX AZ time is not needed.
Hi @Anonymous ,
As @lbendlin has mentioned, Power BI Services operates in UTC time zone, so have to be adjusted using DAX or Power Query by adding offset to UTCNOW().
Thanks,
Pallavi
Yes, I know it is running on UTC time zone. However, I am NOT getting anywhere with the DAX...I am not sure where I am doing this wrong? I tried in Excel and Power BI Power Query....
DAX AZ TIME = DateTimeZone.SwitchZone(DateTimeZone.LocalNow(),-8,0)
Is this expected??
thats is M. Applied step name is automatically generated so DAX AZ time is not needed.
Working now 🙂 Thank you!
Volatile functions like TODAY(), NOW() and the M equivalents are based on UTC. Consider using
UTCNOW() + TIME(8,0,0)
or
UTCNOW() + DIVIDE ( 8,24 )
Replace 8 with your UTC offset
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 11 | |
| 11 | |
| 9 | |
| 8 | |
| 8 |
| User | Count |
|---|---|
| 31 | |
| 28 | |
| 20 | |
| 16 | |
| 15 |