Knowledgebase

Search:     Advanced search

Saving Date/Time Fields with the Helix ALM SDK Changes the GMT Offset

Article ID: 344  |  Last updated: 26 Jun, 2017

If you use the Helix ALM SDK, and save the date in a date/time field, it looks like the GMT offset changes. However, the offset does not actually change. The time being sent back is technically the same time, but it is automatically adjusted to the local time zone with Daylight Saving Time.

For example, using saveDefect, you change the date from 10/10/2007 to 1/1/2007.

The following:

<item xsi:type="ttns:CDateTimeField" SOAP-ENC:position="[1]">
    <recordid>335</recordid>
    <name>CustomDateTime</name>
    <value>2001-10-01T10:10:10-04:00</value>
</item>

is changed to:

<item xsi:type="m:CDateTimeField" SOAP-ENC:position="[1]">
    <recordid>335</recordid>
    <name>CustomDateTime</name>
    <value>2001-01-01T10:10:10-04:00</value>
</item>

When you get the information again, using the Helix ALM Client or SDK, the time is different and the offset is changed. For example:

<item xsi:type="ttns:CDateTimeField" SOAP-ENC:position="[1]">
    <recordid>335</recordid>
    <name>CustomDateTime</name>
    <value>2001-01-01T09:10:10-05:00</value>
</item>

Helix ALM Client users cannot see that the offset changed, so it appears to be a completely different time.

Article ID: 344  |   Last updated: 26 Jun, 2017
Tags
SDK date/time GMT local time

Prev   Next
Field Codes Not Populated in Emails from Helix ALM Automation...     Logging in to Helix ALM After Computer Crashes