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

Value returned from the join class and not the owner class



User is working on a List View on Data-Admin-Operator-ID class and trying to do a join with the same class (Data-Admin-Operator-ID) as ManagerID using pyReportTo of the user ID. User needs to pull manager name in the report. When trying to use ManagerID.pyUserName on display tab, user gets compile error.

When user uses pyUserName on display tab, the value returned is from the join class and not the owner class. (e.g it should return operator name but returns manager name). When used a different class join it worked fine.

Error Messages

Steps to Reproduce

1. Create a List View report in class Data-Admin-Operator-ID with Owner ALL
2. In Pages and Classes tab, add a Page Name "ManagerOP" with Class "Data-Admin-Operator-ID".
3. In Join tab, add a Class join with Prefix "ManagerOP" and Class Name "Data-Admin-Operator-ID". Also, add Edit Conditions with property "ManagerOP.pyUserIdentifier" , condition "Is Equal" and value "pyReportTo".
4. In Display Fields tab, add the following Fields:
a) .pyUserIdentifier
b) .pyUserName
c) .pyReportTo
d) ManagerOP.pyUserName
e) .pyOrgUnit
f) .pyWorkGroup
Add Field Label of your choice

Root Cause

A defect in Pegasystems’ code or rules  is that in List View a class cannot join itself.


Requested the user to use Report Definition since Summary View and List View are deprecated from the Pega versions 7.2 onwards.

Published March 18, 2016 - 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