Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Unique run identifier

Updated on April 6, 2022

When using Business Intelligence Exchange (BIX), you can provide a unique run identifier for each BIX extraction process to mark additions to both parent and child tables in the database, and parent and child CSV files. This enables you to accomplish the following actions after BIX extraction process:

  • Easily identify all inserted records for a particular BIX extract run, both in the main table for a class and in subsidiary tables created for page lists, page groups, and value lists in the class.
  • Delete records from a failed BIX run so that an extract can be re-run without producing incorrect or redundant data.

Two fields have been added to the main table for each extracted class in the database, pxExtractDateTime.TIMESTAMP and pxRunIdentifier VARCHAR(255).

The pxExtractDateTime field has also been added to all subsidiary tables for the class in the database.

The value of the pxExtractDateTime field matches the value of pyLastUpdateTime in the table pr_extract_time for the run. This allows you to perform a join action and obtain all of the records inserted for a BIX run.

You can also include a run identifier through the –k parameter option. For details, see BIX parameters and command-line arguments.

BIX can still run in backward compatibility mode for tables without new fields. If the new fields exist in the database, they are filled in by BIX; otherwise, BIX runs in backward compatibility mode.

  • Previous topic Running an Extract rule by using an agent
  • Next topic Overview of BIX extractions in Pega Cloud environments

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us