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!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
I have a directquery connected to dynamics365 using the sql server connector. I noticed that the date/times are different then what is in the data source. They seem to be adjusted to UTC time when imported to BI. Is there a way to disable the conversion? If it is not possible to convert, then what can I do to convert it back to my local time here and accounting for day light savings time? I am on EST time. Thanks
are you connected to a view or do you also do some transformations in M?
I'm not sure on the impact on the DirectQuery, but I had a case when converting in M to datetimezone type first, and after that converting to date in a separate step gave me correct value
if it doesn't break the DirectQuery, then maybe one of these functions can help (e.g. DateTimeZone.FixedLocalNow)
So i would need to create a new column in power query utilizing the function DateTimeZone? does it account for day light savings time? I will look into this. Thanks
in my case I added 2 separate steps changing type, one changing to type datetimezone, then added another step that changed the type again, this time to date
using functions can also work with added column, but I'm not sure how it affects the DirectQuery connection