Support Article

Number of records does not match-For BIX extracting same class

SA-26329

Summary



A developer is extracting 500 properties from the same class. Three  extract rules have been created on the same class that output to different tables, each has "Use last update time as start" enabled.

Logically, any update on the case will insert a record into all three tables. When they run extracts using the 
Business Intelligence Exchange (BIX) command line process, they see that the total number of records in all the three tables differ.


Error Messages



Not applicable.


Steps to Reproduce

  1. Create three extract rules in the same class and enable "Use last update time as start".
  2. Run BIX extract on all of them.
  3. Check the count of records in each table after the extraction process.


Root Cause



A software use or operation error. As the extract rules are using "Use last update time as start", the filters used for the database queries are slightly different for each extract as they are running sequentially, not simultaneously. Thus, the start time and end time filters used for the database queries will always be different and may end up extracting different work objects.


Resolution



To avoid this and always have the extracts pull the same data, developers should use command line parameters (like –u and –U) for this requirement.

This will require the use of tools outside of Pega (such as a script) to update the values being passed for the parameters as required.

Published August 2, 2016 - Updated August 11, 2016

Have a question? Get answers now.

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