Data Pages loading when no rules mention their use
I've tracked down an issue whereby several data pages are loading into the clipboard at the start of our portal page. I've removed the unnecessary references to these pages but they are still loading. These pages are referencing a report definition and are of type list, editable with scope Thread.
I tried tracing this but can not find reference to where they are being loaded. They are found in the trace at DisplayHarnessWithClass step 4 which is java. Having looked at this java step I cannot work out where it's supposedly calling Activity pxCallRetrieveReportData with the primary page being set to one of the data pages.
Any advice as to how I can track this down?
I should mention we are running Pega 7.31.
***Updated by moderator: Lochan to update Categories***
Are any properties from the data page referenced on the harness being loaded? When tracing, try enabling stream rules, all of the declarative rules, and the data page event types to see if the data page is being invoked from a stream rule or declarative.
Thanks for the advice, it helped me track down the problem.
Seems the issue was due to an incorrectly defined Grid visibility Condition. Where by a property .pySelected was checked for being set to true. However that property was being set to a param value in several data transforms but the param value was set to a string not a boolean as per the property. Changing the param to be a boolean also and changing the affected DT's to set it to boolean instead of string corrected one of the data pages but not the other. However both would have been corrected if not for the below issue.
The other data page issue was caused by the same property being used for searching as was defined in the param for the data page as well as the report definition. Once I substituted the property on the search page to be something else and used that to pass to the data page, that fixed that issue. However I am at a loss as to why this would invoke the data page to load, can you explain?
Also any idea as to why changing visibility conditions sometimes doesn't work the way you'd expect? I re-created my fixes in UAT as a private edit but they weren't working, until I completely changed the condition and put it back!
I tried to test the data page scenario in my environment but wasn't able to reproduce the issue. I also would not expect the issue with the visibility condition where you have to remove it and re-add the same code. If you continue to see issues, please open an SR so someone can review the behavior on your system.