Sharepoint vs PowerBI Time Issues

[DebbieK]

I have a calendar of recurring events in Sharepoint, which I pull through into PowerBI. I recognise that there is a difference between the times displayed as PowerBI is working in UTC whereas Sharepoint is in my local timezone NZT. However - PowerBI appears to be making my appointments LONGER in duration, with the start time being shifted forward by one hour. 

See sample screenshot. My appointment "Clyde" in Sharepoint starts at 11.30AM NZT being 11.30PM UTC, and ends at 5.00PM NZT being 5.00AM UTC. 

When it is imported to PowerBI the start time shows as 10.30PM UTC (an hour earlier) however the End Time shows as expected at 5.00AM UTC. This causes the appointment to have a longer duration. 

Has anyone experienced this? What could the cause be/how could I resolve?

I have not experienced this issue when importing non-recurring calendars or tasks. 

Thanks for any help!

[amitchandak]

@DebbieK , I think this because of timezone

refer

https://sharepoint.stackexchange.com/questions/264660/sharepoint-date-wrong-in-power-bi

https://community.powerbi.com/t5/Desktop/TimeZone-problems/m-p/171245

https://powerusers.microsoft.com/t5/Building-Power-Apps/UTC-Timezone-differences-Power-Apps-SharePoi...

[DebbieK]

Hi amitchandak, thanks for those references. 

I have changed the field type to display timezone and it has given me further information that for some reason the EndDate is in a different timezone to the EventDate (startdate). What could cause this, when both dates are set in the same Sharepoint calendar event at the same time, by the same user? And this occurs ONLY for events which are not all-day events. 

[DebbieK · Accepted solution]

Hi amitchandak, further to my message above I think I have determined the cause. 

Where the EventDate and the EndDate are on different sides of our daylight savings date, is where I am having the issue.

Instead of allowing Sharepoint to use the "no end date" option for the recurring event which sets some arbitrary future date (in this case, which is over the daylight savings boundary), I can use the "End by" function to set my own distant future date which I can ensure is within the same daylight savings window.

This ensures I return dates within the same time zone. 

Thanks again for your support with references. 

[v-yinliw-msft]

Hi @DebbieK ,

Happy to hear you to find the solution of your question.

You can accept your answer as solution to let other people who have the same question with you find the answer easily.

Best Regards,

Community Support Team _Yinliw