Support Article

Reports generate incorrect NULL results and throw errors



Attempting to generate a report to show @Baseclass properties fails under seveal methods. When the report is generated via Obj-brows, most records are returned NULL. When run via report definition, an error is thrown; when run via SQL query, NULL records are returned.

Error Messages

The report definition cannot be saved because of the following error:
Property Name—

** Report Definitions referencing unoptimized properties cannot be saved in Pega rulesets, since customers may choose to disable the required user-defined functions within the DBMS.

Steps to Reproduce

  1. Create a report definition with unoptimized properties.
  2. Try to save it in a Pega ruleset.

Root Cause

An issue in the custom application code or rules: Saving reports with unoptimized properties into Pega rulesets is not allowed.


Perform the following local-change: Save the report into one of the application rulesets.

Published February 2, 2017 - Updated February 4, 2017

Have a question? Get answers now.

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