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

Several InvalidReference Exception when report definition is run



Multiple InvalidReference Exception at the back end when a report definition is run.

Error Messages

Not Applicable.

Steps to Reproduce

  1. Add a data type and add a new column
  2. Create a local data source. This creates a new table
  3. Create a report definition in the same class including a newly created column
  4. Run the created report definition

Root Cause

The 'Report on Descendent classes' instances option on the Data Access tab of the Report Definition rule has a new option to include data from all the descendant classes of the report's primary class. If the descendant classes are mapped to multiple class tables, the generated SQL query performs UNIONs to include this data. Previously, only a single class was included in the report.


 Perform the following local-change:

Open the report definition Data Access tab and disable the 'Report on Descendent classes' check box.


Published August 15, 2019 - Updated December 2, 2021

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