Date-Time in production report not displaying correctly in comparison to test version/workspace?

[pborah]

This is a bit odd?

So in desktop when designing the report, in Power query, I created a last refreshed date table by using -

= DateTimeZone.SwitchZone(DateTimeZone.UtcNow(),-4)

Which works exactly as expected both locally and when published to service in the Test workspace. When I deploy this to the production workspace using the deployment pipeline, things act in a strange manner and the time shows UTC instead of the -4 hours offset which is Eastern Time. I have double, triple checked that I deployed the correct report and semantic model. 

Any ideas as to what is going on?

[Anonymous]

Hi @pborah 

Did Sahir_Maharaj 's method solve your problem? If yes, could you please mark it as a solution? This will be of great help to other users experiencing similar problems. Thank you!

If you have any further questions, please feel free to contact me.

Best Regards,
Yulia Xu

[Sahir_Maharaj · Accepted solution]

Hello @pborah,

Although Power BI generally uses UTC for service operations, differences in regional settings between workspaces could lead to this behavior.

Can you please try this approach:

LastRefreshedDate = 
DateTimeZone.RemoveZone(DateTimeZone.ToLocal(DateTimeZone.UtcNow()))

Hope this helps.