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

Report is failing because pxObjClass is in OR condition in RD

SA-35354

Summary



When user is running report definition, user gets no result and error occurs in Tracer
" ** pxObjClass cannot be associated with OR in the filter logic."

Original condition which receives the error:
A OR B OR (A AND B) AND C
where condition C is: .pxObjClass is equal D_AppContext ClassNames(Bo....

Updated condition (which does not receive error):
“A AND B AND (A AND B) AND C”

Error Messages



EXCP001 alert:
[email protected]*Rule-Obj-Activity:pzTransformAndRun*RULE-OBJ-REPORT-DEFINITION PXRETRIEVEREPORTDATA #20160614T132614.161 GMT Step: 33 Circum: 0*27**NA*NA*Embed-ReportContent*NA*Embed-ReportContent*NA*Reporting**NA**;doActivity Rule-Obj-Report-Definition;Java;RULE-OBJ-ACTIVITY RULE-OBJ-REPORT-DEFINITION PXRETRIEVEREPORTDATA #20160614T132614.161 GMT Step: 33 Circum: 0;doActivity Rule-Obj-Activity:pxRetrieveReportData;18 additional frames in stack;*NA*

ERROR: ** pxObjClass cannot be associated with OR in the filter logic.


Steps to Reproduce



1.Create a report definition.
2.Add a declarative index join in Data Access tab.
3.Add some properties in the report.
4.Add three filter conditions and make sure one of the column source is .pxObjClass.
5.Enter the below filter condition and make sure the condition value for .pxObjClass is "C" and few of the properties are declarative index join property.
A OR B OR (A AND B) AND C.



Root Cause



In previous versions of PRPC incorrect query was being generated for the report having joins and filters with pxObjClass and OR logic, inorder to avoid that incorrect behavior, this validation message was introduced during run time of the query instead of giving the incorrect results.

Resolution



This is an expected behavior, if the report definition is configured with any Joins(Class join/declaritive index join/Association/SubReport) and having a filter logic with pxObjClass and OR logic then a validation message will be thrown "pxObjClass cannot be associated with OR in the filter logic"during run time of report.

Published April 17, 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