UTC, GMT Issue for Reports Built from D365

Hi All,

Apologies for getting back late to this.

I resolved the issue but my solution is just a patch, i would prefer something more substantial

so I have a ticket open with MS to discuss.

Anyway, so I ran a series of tests on one single time entry and followed it from the power query editor to Power BI desktop to Power BI Service.

First I set the data to Date\time to dsiplay the time stamp also. Then I created a new column in the Power Query editor to copy the date column (column with my time entries) and apply some timezone changes to it.

I done this for three times 0, +3, -3.

For example, DateTimeZone.SwitchZone([date], 3))

As you can see the time entry is timestamped at midnight and as you can see from the 0 row the entry actually goes back a full day when published to the service! This is why my small changes of 1 or 2 hours wasn't making any difference.

To verify my finding I just went with the original date column (took out the new query) and followed the same time entry through the desktop and service and it too appeared a day before in the service.

To get around this I used a simple DAX expression dateadd(timeentries[date],1,DAY)

Which creates a new column with one day added to the time entries. Now my desktop data is one day ahead but it's perfect in the service so the users are happy.

This is not my preferred long term solution and I'm working with MS to see if we can do anything else.

Thanks,

Jason

Hi All,

I tried a lot of Power Bi related fixes and none seemed to fix it.

I eventually moved all users timezones in D365 back to standard UTC and that solved the issue.

However, if Europe decides to get rid of daylight savings and stay on summertime all year then we will need to look at a bigger solution.

Jason