V1.0.30.0 – Time fields not working correctly?

Forums Modern DFFS V1.0.30.0 – Time fields not working correctly?

Viewing 4 reply threads
  • Author
    Posts
    • #36995
      Wendi Watson
      Participant

      Hello Alexander,

      I have noticed when I use the time field that the time on the record in the SharePoint list is different than the time on the form. I tested this to make sure it was not a setting on my SP site and it does not seem to be so I am wondering if it is in the DFFS code? I am attaching examples for you to check.

    • #36998
      Alexander Bautz
      Keymaster

      I have tried to address this problem in version 1.0.28.0 and 1.0.29.0, but there might be more to this than I thought.

      If you edit an existing record – does the date and time show the same as in the list view or is it offset X number of hours?

      Can you please post the result when you bring up the developer tools (hit F12 and select Console) and type in this to show the user time zone

      _spPageContextInfo.userTimeZoneData
      

      And this to view the web time zone

      _spPageContextInfo.webTimeZoneData
      

      Click the little triangle to expand the results so you get something like this:

      {
          "Description": "(UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna",
          "Bias": -60,
          "Id": 4,
          "DaylightBias": -60,
          "DaylightDate": {
              "Year": 0,
              "Month": 3,
              "DayOfWeek": 0,
              "Day": 5,
              "Hour": 2,
              "Minute": 0,
              "Second": 0,
              "Milliseconds": 0
          },
          "StandardBias": 0,
          "StandardDate": {
              "Year": 0,
              "Month": 10,
              "DayOfWeek": 0,
              "Day": 5,
              "Hour": 3,
              "Minute": 0,
              "Second": 0,
              "Milliseconds": 0
          },
          "WorkHours": {
              "WorkDayStartHour": 480,
              "WorkDayEndHour": 1020,
              "WorkDays": 62
          }
      }
      

      Alexander

    • #36999
      Wendi Watson
      Participant

      When I edit an already existing record it brings up the correct date. The wya I got around this is to do a Convert Time in my PowerFlow with an offset of 11 hours by using (UTC) Coordinated Universal Time -11. I have attached another document with screenshots and the information you asked for from the Tools Console

    • #37001
      Wendi Watson
      Participant

      adding this as I am not sure I grabbed the correct information
      “webTimeZoneData”: {
      “Description”: “(UTC-06:00) Central Time (US and Canada)”,
      “Bias”: 360,
      “Id”: 11,
      “DaylightBias”: -60,
      “DaylightDate”: {
      “Year”: 0,
      “Month”: 3,
      “DayOfWeek”: 0,
      “Day”: 2,
      “Hour”: 2,
      “Minute”: 0,
      “Second”: 0,
      “Milliseconds”: 0
      },
      “StandardBias”: 0,
      “StandardDate”: {
      “Year”: 0,
      “Month”: 11,
      “DayOfWeek”: 0,
      “Day”: 1,
      “Hour”: 2,
      “Minute”: 0,
      “Second”: 0,
      “Milliseconds”: 0
      },
      “WorkHours”: {
      “WorkDayStartHour”: 480,
      “WorkDayEndHour”: 1020,
      “WorkDays”: 62
      }
      },
      “webTime24”: false,
      “webFirstDayOfWeek”: 0,

    • #37002
      Alexander Bautz
      Keymaster

      Thanks for the information. I see that you have not set a preferred timezone (userTimeZone is null). There is a problem in the code that does not properly offset the date and time according to the web time zone when the user time zone is null (the offset is necessary because SharePoint stores all dates as UTC).

      I’ll look into that in the next version, but I think your problem can be fixed (for your user) if you set the timezone on the user by following these instructions: https://support.microsoft.com/en-us/topic/change-your-display-language-and-time-zone-in-microsoft-365-for-business-6f238bff-5252-441e-b32b-655d5d85d15b

      Let me know if that fixes it.

      Alexander

Viewing 4 reply threads
  • You must be logged in to reply to this topic.