Question
Accenture
AU
Last activity: 7 Jun 2022 3:28 EDT
Unoptimized property performance warnings when using subreports
Hi all,
We are getting unoptimised property performance warnings for a report when using sub reports. The properties have been optmised.
"These properties are not optimized, and using them to join a sub report will result in very poor performance"
The warning does not display if we remove the subreports and the warnings do not show in the subreports themselves.
The subreport and the parent report are in the same class. The warnings are for properties used by both the parent and subreports.
To summarise, the performance warning does show in the parent with the subreports removed - and does not show in the subreports at all. However, it does show in the parent when the subreports are added.
Any assistance would be appreciated.
Thanks,
Richard
***Edited by Moderator Marije to add Capability tags***
Updated: 26 May 2022 5:39 EDT
Pegasystems Inc.
GB
@RichardD8276 if columns are optimized then the warning should disappear.
There are two ways to optimize the columns:
1.through the UI 2. through prpcUtils or prpcServiceUtils from Command line
Here are some troubleshooting ideas:
Has there been a change in the class mapping? Has the underlying database changed?
Could you please check to make sure to optimize the relevant _work table?
We have also seen this issue if the Columns names were not in the right case.
Is it possible that only a few properties are showing in the error while editing the main report?
Are those properties added in a filter condition?
Can you confirm you followed the recommendation in the SysAdmin documentation Planning for property optimization?
@RichardD8276 also see the below forum users' suggestion for you:
1. try resaving the DataTableEditorReport report definition once of this class to check if there are any issues with the current fields.
2. Try saving the Data-Admin-DB-Table instance of the Property class and then do a test connectivity afterwards. Then check the report if it still shows you the same warning.
HCL Technologies B.V.
NL
@MarijeSchillern Also try resaving the DataTableEditorReport report definition once of this class to check if there are any issues with the current fields.
Aaseya IT Services Pvt LTD
SA
Try saving the Data-Admin-DB-Table instance of the Property class and then do a test connectivity afterwards. Then check the report if it still shows you the same warning.
Accenture
AU
Hi @MarijeSchillern,
Thanks everyone for the replies.
I am not sure its a simple optimisation issue.
- All the properties appear to be optimised (confirmed as columns in the database, they have values and they are externally mapped on the class)
- There are no optimisation warnings in the subreport.
- There are no optimisation warnings in the parent unless the sub report is added
Is that a bit clearer ?
Pegasystems Inc.
GB
@RichardD8276 I would suggest that you log a support incident for this to allow our support team to investigate this in more depth.
If you go this route could you please provide the INC id here so that we can help track it?
Pegasystems Inc.
IN
Hey @RichardD8276,
If you are using any of the sub-report columns in the report filter, try to update the filter columns in the report with non-empty captions.
It is a recent platform issue and non-empty captions is the workaround. Please check if its the same.
Lventur
IN
Please check in any of the report Option - Report on descendant class instances - checkbox was selected under Data Access tab unwantedly.
If yes please unselect the option and try once.
Accenture
AU
@Gunasekaran Baskaran I will check, thanks.
Pegasystems Inc.
IN
Hi @RichardD8276,
Could you please respond to the below
1. Confirm if you are using any of the sub-report columns in the report filter?
2. Are you using function alias in these filters?
3. Are the filters in the report left with non-empty captions?