Re: After MS Update Time stored with Offset

Anson Hidajat — Fri, 09 Nov 2012 15:34:50 GMT

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.

After MS Update Time stored with Offset

hickorysmokebbq — Thu, 08 Nov 2012 14:35:40 GMT

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.

Comments??

General

Re: After MS Update Time stored with Offset

After MS Update Time stored with Offset