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

InvalidReferenceException occurs on executing reports



InvalidReferenceException occurs  on executing reports. This occurs despite exposing the report properties.

Error Messages

Error: ** ** InvalidReferenceException OpID.pyAccessGroup Unexposed properties cannot be selected for classes mapped to external tables

Steps to Reproduce

  1. Create a report definition in the Work class.
  2. Add an Operator class Join with a worklist.
  3. Execute the report.

Root Cause

A backwards compatibility defect in Pegasystems’ code or rules.
The report definition has a Join on the Data-Admin-Operator-ID which also has an Implementation class. Since the 'Report on Implementation classes' option is enabled, it applies for the Join class as well. The exception occurred because the Implementation class of the Data-Admin-Operator-ID is mapped to an external table and the Join properties used in the report are not exposed in the external table.


Here’s the explanation for the reported behavior:

Prior to Pega Platform 7.3.1, the 'Report on Implementation classes' option did not apply to the Join class and but only to the applies-to class. Hence, exceptions do not occur for the same report. However, this behavior changed as of Pega Platform 7.3.1.

Published June 3, 2020 - 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