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 including unwanted classes in query

SA-28317

Summary



In BiX using the switch -c in a script pulls in more classes than expected.


Error Messages



Not Applicable

Steps to Reproduce



Extract using the -c switch on the command line.


Root Cause



Incorrect system behavior is observed when using the -c switch from the command line More than the expected or wanted classes are extracted.


Resolution



Here’s the explanation for the reported behavior:

The behavior is expected. A
ll concrete descendants of the current class for -c option whether pattern inherited or directed are selected.

In the past BIX used a like predicate even though the root class to extract was not a class group. This led to inefficiencies and data extractions that retrieved all inherited classes.
This defect was corrected. However, in order to have some method to mimic this behavior a -c option was created. This option will not only extract pattern inherited classes, but also directed inherited classes. This can cause other unexpected results.

​The below table illustrates what happens.This behavior is as designed and is expected behavior. When extracting History-X-Y, the items in red are also extracted with the -c argument. These are directed inheritance. The prior behavior would return only the pattern inheritance via the like predicate. E.G. select <columns> where ... pxObjClass like 'History-X-Y%'


Class Name Class Type Derives From
History-X-Y Concrete History-X-Z
History-X-Y-Data-Account Concrete History-CS-FW-Z-Data-SR-Y
History-X-Y-Data-AccountInfo Concrete History-X-Y
History-X-Z Concrete History-CS-FW-Z-Work
History-X-Z-W Concrete History-CS-FW-Z-Work-W
History-X-Z-W-Data-RED Concrete History-Data-
History-X-Z-W-Data-YELLOW Concrete History-Data-
History-X-Z-W-Data-CI-IRA-CO Concrete History-Data-
History-X-Z-W-Data-Notification Concrete History-Data-
History-X-Z-W-Data-Product Concrete History-Data-
History-X-Z-W-Data-BLUE Concrete History-Data-
History-X-Z-Acct Concrete History-CS-FW-Z-Work-Acct
History-X-Z-CC Concrete History-CS-FW-Z-Work-CC
History-X-Z-DC Concrete History-CS-FW-Z-Work-DC
History-X-Z-DC-Return Concrete History-CS-FW-Z-Work-DC
History-X-Z-Data-ClYsLookup Concrete History-CS-FW-Z-Data-ClYsLookup
History-X-Z-SR Concrete History-CS-FW-Z-Work-SR
History-X-Z-SR-AM Concrete History-CS-FW-Z-Work-SR
History-X-Z-SR-CB Concrete History-CS-FW-Z-Work-SR
History-X-Z-SR-MM Concrete History-X-Z-SR
History-X-Z-SR-RSO Concrete History-CS-FW-Z-Work-SR
History-X-Z-SR-SS Concrete History-CS-FW-Z-Work-SR
History-X-Z-SR-SS-RAIF Concrete History-CS-FW-Z-Work-SR
History-X-Z-SR-TOA Concrete History-CS-FW-Z-Work-SR
History-CS-FW-Z-Work-SR Concrete History-Work-Cover-
History-CS-FW-Z-Work-SR-AU Concrete History-CS-FW-Z-Work-SR
History-CS-FW-Z-Work-SR-CB Concrete History-PegaFS-SCM-Work
Suggest Edit

Published March 26, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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