...
The browser's time zone can be overidden by appending the &_fomTz=<tz> parameter to your form’s share URL. For Example, the timezone of a Product Order form running in the EDT timezone that has a Order Date /Time control can be changed to the PST timezone by appending the &_formTz=America/Tijuana parameter to the form's share URL. If 7:13 is entered for the time value, the time in the XML document will be stored as if the browser was running in the America/Tijuana timezone. In the example below, the T14:13:00Z represents 7:13 - EDT plus 7 hours which is the offset for the America/Tijuana timezone. See Time Zones for more information.
...
| Warning | |||
|---|---|---|---|
In order to export data to Excel you must setup your form fields as saved fields as described | Submission Data | Submission Data | here.
Click the Excel icon at the top of the table to view the submission results in Excel. The spreadsheet reflects the submissions that are displayed in the table (filtered by date).
...
Time and date time values exported to Excel are submitted UTC values from the submission doc. Time data will be displayed in the Excel spreadsheet in UTC format. For Example: The Product Order Spreadsheet shows the data from two customer orders entered at 9:00 AM and 2:30 PM in the Eastern Standard Time Zone. Time data will be converted to UTC and stored in the xml document. Exporting the submissions data to Excel will show the time data converted to UTC as it is in the xml document. See the Order Time column in the image.
. Notes on Export Column Ordering
The export to Excel spreadsheet function available in the submission repository reporting screen will now export the saved fields in a column order from left to right that matches the saved field ordering on the saved fields dialog (see section 2) as shown from top to bottom. Note that the submissions meta data is still listed first and the ordering of that data is not available as part of this enhancement.
The submissions export gets a bit more complex with groups and especially with repeating groups. Previously, the export would always maintain fields in groups and repeating groups in adjacent columns. This is no longer possible with user specified ordering of columns. This can make the export slightly strange when you look at it, but the user specified ordering must always work.
Figure 3.1 - SR Export illustrating a break in a group
One outlier case to be aware of is as follows. Suppose a set of saved fields is specified and multiple submissions are made. Then suppose that the designer removes some saved fields, leaving only some others. In any export of the previous submissions, the saved fields shown in the export will be ordered by the current set of saved fields, with any previously saved fields which are present in the submission but not in the current list simply added on as the right-most columns. If a field was saved as part of a submission, it is always included in the export.