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

Child classes instances not picked when we run bix extracts



Child classes instances are not picked when user execute Business Intelligence Exchange (BIX) extracts which are present in the parent class.

Error Messages

Not Applicable

Steps to Reproduce

1.Open a BIX extract rule which is present in parent class.
2.Execute it.

Root Cause

A defect or configuration issue in the operating environment.

Issue is that in earlier version of BIX were taking advantage of the bug that would use a "like" in the where clause instead of an "=" even when the class was not a classgroup.

Extracts are specified at the class level, not at the application level.

For example, if there are three case types in the application and would like to extract data for each, one must define an extract rule for each of the three case types.

Note: When extracting from a class group, the extract will include all classes in the class group. If the class is not a class group, the extract will only include instances of that class.

Similar to other areas of the product (like List Views, Report Definitions etc.), when a rule is defined at the classgroup level, BIX will include its subclasses by using a LIKE query.

But for classes which themselves are not a classgroup but belong to one, then BIX does not generate a LIKE query.

There was a bug in Extract rule executions which have been fixed to keep the behavior consistent with other rules.


In BIX 7.2.2 there is a new feature which will allow the standard filters to be removed from the extraction query.

There is a secondary option to also remove the order by clause from the query. The feature has been backported to Pega 7.2.1

With this feature one can mimic the same behavior user was seeing in previous release of BIX.

This feature involves both code and rule changes. These are the installation instructions.

1. Using Hot Fix Manager install DL item containing HFix-33290 and its dependent hot fixes

2. Import HFix-33295.jar using Import Utility

3. Restart all nodes

After this when you open your Extract rule on the "Filter Criteria" tab, see a checkbox to "Skip Standard Filters".

With this checked the standard "pzInsKey like" for a classgroup or the "pxObjClass =" for a class will not be included in the generated extraction query.

There is a second checkbox "Skip standard order by clause".

​ With this checked the standard order by pzInskey clause to the generated extraction query.

Published April 10, 2017 - 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