Reports generate incorrect NULL results and throw errors
SummaryAttempting 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 MessagesThe report definition cannot be saved because of the following error:
** 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
- Create a report definition with unoptimized properties.
- Try to save it in a Pega ruleset.
Root CauseAn issue in the custom application code or rules: Saving reports with unoptimized properties into Pega rulesets is not allowed.
ResolutionPerform the following local-change: Save the report into one of the application rulesets.
Published February 2, 2017 - Updated February 4, 2017