Form Time Field off by 1 hour - InfoPath Dev
in

InfoPath Dev

Form Time Field off by 1 hour

Last post 03-14-2016 03:54 PM by PMOdave. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 03-14-2016 03:06 PM

    Form Time Field off by 1 hour

    Hi guys,

    I have a client with an old form running on SP2007. Since the daylight savings time change on the weekend, the times on their old forms (new ones are fine) are off by one hour. Note the time is only wrong in the form (form filler type) they are correct in SP. New forms created are fine, old ones are not.

    Other weird thing that may or may not be related, the field type is set to time and when I enter a time, eg. 09:00, it looks fine on the form, but the XML creates a time RANGE from that time. So my 08:00 becomes 08-00:00-07:00 ?????

    In the XML it looks like <my:StartTime>08:00:00-07:00</my:StartTime> 

     

    HELP

     

     Similar to discussion here, but with no solution:

    https://social.msdn.microsoft.com/Forums/sharepoint/en-US/95311446-08ea-4d96-9e1d-63babfd8d729/sharepoint-2010-and-infopath-wrong-time-in-infopath-filer-after-dst-change?forum=sharepointcustomizationprevious  

  • 03-14-2016 03:54 PM In reply to

    Re: Form Time Field off by 1 hour

     Ok I figured out the second part, it's not a time range. The second portion is the time offset from UTC time.

     So, when I look closer:

     For an older form (from last week) where the time is displaying correctly, the offset is of 6 hours

     <my:FinishTime>16:00:00-06:00</my:FinishTime>
     <my:StartTime>08:00:00-06:00</my:StartTime>

     For a new form (from today) where the time is wrong, the offset is 7 hours.

      <my:FinishTime>15:00:00-07:00</my:FinishTime>
     <my:StartTime>09:00:00-07:00</my:StartTime>

     

    This all seems logical, or am I just tired?

    First off, why is SP displaying the time WITH the offset in the SP List Column? Eg: "09:00:00-07:00"

Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.