Daylight savings time change issue

[jclum]

Hello - 

We have a number of shared schedules that seem out of sync post DST change .  The names of the schedules on the left are correct but the schedules, on the right, are off by exactly 1 hour.   The reports that utilize these schedules are refreshing at the correct time which adds to the confusion.   Has anyone encountered this issue? 

The report server has been re-started post the DST change.  We are on the May 2023 release of PBI RS.  

Thank you.

Jeff Clum

[v-rongtiep-msft]

Hi @jclum ,

There is indeed a UTC reason as @lbendlin  said. 

You can use DateTime.AddZone function to achieve your requirement. This function adds the timezonehours as an offset to the input datetime value and returns a new datetimezone value.

DateTime.AddZone([CreatedOn],1)

I have also found a helpful post, please refer to.

Solved: Convert UTC to client time zones? - Microsoft Fabric Community

How to Get Your Question Answered Quickly - Microsoft Fabric Community

If it does not help, please provide more details with your desired output and pbix file without privacy information (or some sample data) .

Best Regards
Community Support Team _ Rongtie

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[lbendlin]

That's one of the reasons why all your schedules should be created in UTC.

[jclum]

@lbendlin & @v-rongtiep-msft,

Thank you both for your replies. To clarify, this issue appears in the report server web interface
under Site settings -> schedules. Within this interface I am unclear about using a UTC time as suggested.
There is no option for a date time function, only hour, minute and AM/PM selection. To add, we do have a test report server with the a similar configuration (fewer schedules) that did not present this issue. I have
compared the time zone settings on both servers and found no differences. The repository databases for both report servers are on separate database servers and the time zone settings on those database servers match the settings of the report servers.