Forum Discussion

ryan87's avatar
ryan87
Regular Visitor
8 years ago

UTCNOW() incorrect on web version

Hi,

 

I have a report which has a visual that shows when the report last refreshed by using the UTCNOW() function. However since the daylight savings changed by 1 hour, the time on the web version is 1 hour behind the time that the report last refreshed. So the scheduled refresh time is correct however the time displayed using this formula is 1 hour behind. Although it is correct in the desktop version.

 

Without adding +(1/24) to my formula, can anyone please advise how I can correct this? The format of the visual is HH:MM

 

Thanks

 

3 Replies

  • Hi ryan87,

     

    What's the Time Zone setting on your local machine? And why did you make the daylight savings changed by 1 hour? Could you please make a more detailed description about your issue? So that I can make some proper tests.

     

    Thanks,
    Xi Jin.

    • ryan87's avatar
      ryan87
      Regular Visitor

      Hi v-xjiin-msft, jthomson,

       

      I haven't changed anything, the physical time changed by 1 hour due to daylight saving and since that, the time on the web version of the reports has been 1 hour in the past, so it clearly looking at the wrong time. The time for the same visual on the desktop is correct, so I don't think it anything to do with my time settings on my desktop (below).

       

      Machine settings: Time Zone (UTC+00:00) Dublin, Edinburgh, Lisbon, London

       

      I have just checked and my machine settings are exactly the same as the Time zone settings of the scheduled refresh, whcih is taking place on time. However the visual with UTCNOW() is incorrect.

       

      It's now 11.55am so as per below, the last refresh took place at 11:00am which took 9 minutes, but the visual on the report says 10:09 as below.

       

      Any other suggestions would be appreciated.

       

       

       

      Thanks

  • jthomson's avatar
    jthomson
    Solution Sage

    UTC isn't affected by daylight savings so this should be intended behaviour