Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Date does not change as per the timezone selected



While extracting data through command line in Business Intelligence Exchange (BIX), user passes timezone ("-J" "Europe/London") as an argument such that the date field gets converted to the required timezone and is extracted accordingly. The application and data base servers are set to Amsterdam timezone. Requirement is to extract the data as per London's time. This works as expected during the daylight saving time (i.e. BST hours which is GMT+1 during the summer time). The timezone must have changed and the date must have converted to GMT dates due to the timezone parameter when the daylight saving period gets over and the GMT starts. However, the date still remains in the BST hours i.e. 1 hour ahead of GMT.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a Business Intelligence Exchange (BIX) extract rule on the Designer Studio
  2. Pass the -J Europe/London parameter in BIX.xml or while running the standalone command
  3. Verify if the records are being extracted correctly and the Date and Time is as per the timezone

Root Cause

When the timezone is set to Europe or London, Calendar.ZONE_OFFSET is used in which is mapped to Jan 01 1970. The timezone of London is UTC+1hr in this case. Hence, the extracted dates are converted to UTC+1 on specifying the Europe or London timezone.


Apply HFix-60159.


Published February 10, 2020 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us