Skip to main content

DateTime Field Behavior After Changing Your Time Zone

Zuora

DateTime Field Behavior After Changing Your Time Zone

This article describes the behavior of dateTime fields after you change your time zone. The article provides example values of dateTime fields for the SOAP API, Data Source Exports, and Export ZOQL.

For more information about changing your time zone, see Before Changing Your Time Zone.

The Behavior of Which Fields is Affected When I Change My Time Zone?

  • If you are using WSDL 69 or later, the behavior of all dateTime fields is affected when you change your time zone. The behavior of date fields does not change when you change your time zone.
  • If you are using WSDL 68 or earlier, the behavior of all dateTime fields is affected except for the fields listed in Date Field Changes in the SOAP API. The fields listed in that article became date fields in WSDL 69 and later, and changing your time zone does not affect how they behave.

Example DateTime Field Values

The following sections show example values for dateTime fields in the SOAP API, Data Source Exports, and Export ZOQL. The examples all assume that:

  • You have changed your time zone to Europe, Paris (GMT+01:00).
  • Zuora system time is Pacific Standard Time (GMT-08:00). Note that Zuora system time might also be Pacific Daylight Time (GMT-07:00) depending on the time of the year. See Date and DateTime Format for more information.

SOAP API

Example field: Usage.StartDateTime

Example Input Value Response Value Explanation

2015-01-01T16:00:00

2015-01-01T16:00:00+01:00

If you do not enter a time zone offset, your tenant time zone offset is added automatically.

2015-01-01T16:00:00+01:00

2015-01-01T16:00:00+01:00

If you input your tenant time zone offset, the value remains unchanged.

2015-01-01T16:00:00+04:00

2015-01-01T13:00:00+01:00

If you input a time zone offset different than your tenant time zone, the value is converted into your tenant time zone.

Data Source Exports

Example field: Subscription.CreatedDate

Value in SOAP Response Value in CSV File Explanation

2015-01-01T16:00:00+01:00

2015-01-01T16:00:00+01:00

DateTime fields always have your tenant time zone offset.

2015-01-01T09:00:00+01:00

2015-01-01

If the field value is midnight in Zuora system time, the CSV file only has the date part of the field value.

In this example, 2015-01-01T09:00:00+01:00 is equal to 2015-01-01T00:00:00-08:00, which is midnight in Zuora system time, so only 2015-01-01 is included in the CSV file.

Note: If you are using WSDL 68 or earlier, the CSV file only has the date part of the field value even if the field value is not midnight in Zuora system time.

 

When you perform a data source export from the Zuora UI, the date format will be localized based on the Locale configured in Settings > Administration Settings > Manage Tenant Profile. See Managing Your Tenant Profile for more information.

Export ZOQL

Example field: Account.CreateDate

Export ZOQL Query Input Value in CSV File Explanation

Account.CreateDate=2015-01-01T16:00:00

2015-01-01T16:00:00+01:00

If you do not enter a time zone offset, your tenant time zone offset is added automatically.

Account.CreateDate=2015-01-01T16:00:00+01:00

2015-01-01T16:00:00+01:00

If you input your tenant time zone offset, the value remains unchanged.

Account.CreateDate=2015-01-01T16:00:00+04:00

2015-01-01T13:00:00+01:00

If you input a time zone offset different than your tenant time zone, the value is converted into your tenant time zone.

Account.CreateDate=2015-01-01T09:00:00+01:00

2015-01-01

If the field value is midnight in Zuora system time, the CSV file only has the date part of the field value.

In this example, 2015-01-01T09:00:00+01:00 is equal to 2015-01-01T00:00:00-08:00, which is midnight in Zuora system time, so only 2015-01-01 is included in the CSV file.

Note: If you are using WSDL 68 or earlier, the CSV file only has the date part of the field value even if the field value is not midnight in Zuora system time.