After MS Update Time stored with Offset - InfoPath Dev

InfoPath Dev

Use our Google Custom Search for best site search results.

After MS Update Time stored with Offset

Last post 11-09-2012 07:34 AM by Anson Hidajat. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 11-08-2012 06:35 AM

    After MS Update Time stored with Offset

    We have had a few issues recently from a MS update that changed the way InfoPath stores time.  Time was stored as 06:00:00.  Now it includes the offset  06:00:00-4:00.  This is further compounded by the recent time change.  Forms that were submitted before Saturday night now show every time one hour earlier than they did before the time change.  

    This is only visible in the xml data.  Has anyone seen this?   It seems be causing more trouble than it's worth especially if your time changes twice a year.

    It seems to happen only when a time value is entered into a time field.  The now() function does not seem to include the offset.



  • 11-09-2012 07:34 AM In reply to

    Re: After MS Update Time stored with Offset

    Time zones can be difficult to manage in InfoPath.  Especially when you throw in client vs. server behavior.  The best thing to do is to just have InfoPath handle the time zones itself.  For the most part it does the calculations correctly.  If you need to manually override, unfortunately InfoPath doesn't provide an easy way to do that.  You will have to use substring functions to add back the time zone piece yourself and then take it from there.
    Anson Hidajat
    Qdabra® Software/
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™

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