Report Definition has Failure to access un-optimized Property
SummaryUsers notice when they refer to an un-optimized property in Report Definition an error is shown on screen at design time when performing a save operation.
Error MessagesProperty Name: This is not a valid property.
Steps to Reproduce
- Create a New Report Definition.
- Under columns to include, refer an un-optimized property.
- Save the Report Definition.
Root CauseExpected Behavior
ResolutionHere’s the explanation for the reported behavior:
The feature to refer un-optimized property in Report Definition i.e. direct BLOB access in Report Definition was introduced in Pega 62SP2. It is not available in Pega 61SP2.Report Definitions with references to un-optimized BLOB properties generate SQL that calls user-defined functions (UDFs) that open and access property values directly from the BLOBs stored in the DBMS.These UDFs are automatically installed in the DBMS when v6.2 SP2 is installed or a previous PRPC version is upgraded to v6.2 SP2.
Also, poor performance is very likely if un-optimized properties are used as sorting or grouping columns in reports, or used in filter conditions, in reports on classes with more than a few hundred instances.
Optimize the property to refer it in Report Definition in Pega 61SP2.
Published April 27, 2017 - Updated May 5, 2017