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

Need to reset last update date for BIX extract



While attempting to set up BIX you are receiving duplicate work objects from a previous extract.
​You have updated your extract rule and run a full extract, and now have a number of duplicate work objects.


The explanation for this behavior is as follows:
The pyLastUpdate column in the pr_extract_time table tracks the last update time for BIX extraction. No special permissions are required to run a SQL query against this property.
Under special circumstances you may want to change the value of the pyLastUpdate column, and this can be done using direct SQL.
This property is automatically updated after each run of BIX. Always take a backup of the data that you are changing before making modification.

Published July 7, 2015 - Updated October 8, 2020

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