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

Difference in datetime and boolean BIX DB vs XML extract 7.1.8



When extracting a boolean property to a target database table it is stored in the database as 0 or 1. Similarly when extracting a datetime property to a target database table the time is adjusted to the correct timezone. However, when extracting the same boolean and datetime property to an XML file the format of the outputted values is not the same. For boolean properties it is output as true/false and for datetime the time is in GMT,

Error Messages

Not applicable

Steps to Reproduce

Run a DB extract of a boolean and datetime property. Run the extract of the same properties to XML.

Root Cause

A defect in Pegasystems’ code or rules when extracting a DateTime property to XML output format , the data is first read from blob where all datetime properties are stored in GMT Format then put it into XML format in GMT format.

However while extracting a DateTime property to DDL output format, the data is first read  from blob where all datetime properties are stored in GMT Format then it will be inserted into the target database based on target database timezone, which is done based on JDBC drivers.

So Extracting a datetime property into XML format gives you the GMT format and extracting the same datetime property into Database outformat gives the target database timezone format.


Apply HFix-25884 which provides a new command line option J to take in a user specified time zone for e.g., UTC+05:00 format(s); If the specified is not valid, it defaults to GMT 

example :How to specify this option: "-J" "UTC+5:30" 

Now the output for Date time properties will be written in UTC+5:30 time zone. 
Please note that if you specify time zone as UTC + 5:30 then there will get a validation message in the logs saying “Timezone specified for datetime properties formatting is " + invalidTimeZone + " and timezone considered is GMT. Please ensure that specified format doesn't have space(s) between timezone and the offset.

Suggest Edit

Published February 9, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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