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

BIX Extract does not extract all records



The Business Intelligence Exchange (BIX) based on the 'Last Updated Time as Start' filter fails when executed using the Job Scheduler.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a BIX Extract rule.
  2. Execute the rule using the 'Last Updated Time as Start' filter.

Root Cause

This behavior is as per Pega product design.


BIX extracts records using the 'Last Updated Time as Start' by comparing the pylastupdatedate in the pr_extract_time table and the pxcommitdatetime column in the relevant work table. Hence, among the records which are not transferred during the time when the extract is not processed completely, the work objects which are updated later to that date are already transferred to the target database.

For the rest of the records, perform the below steps:
  1. Create a copy of the BIX extract.
  2. Disable the 'Last Updated Time as Start' filter.
  3. Apply manual filters to specify the pxcommitdatetime > the DateTime of the last successful execution before extraction failure and pxcommitdatetime < the DateTime when the extract is processed 100% successfully.
  4. Manually run the extract.

This transfers any lingering work object records that were not transferred during that timeframe and which were not updated since.

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