Question
JCS Lanit - BPM
RU
Last activity: 4 Oct 2018 11:08 EDT
Accessing data from pxPages in a Tree Grid repeating layout
Hi,
I'm using a tree grid repeating layout on a section to display a tree of cases that match some criteria based on current case's context. I've decided to use a page list property as a source because dependent cases should be loaded lazily as a user expands a row with a root case. To be more specific, I'm using pxResults property on a page of Code-Pega-List class.
Hi,
I'm using a tree grid repeating layout on a section to display a tree of cases that match some criteria based on current case's context. I've decided to use a page list property as a source because dependent cases should be loaded lazily as a user expands a row with a root case. To be more specific, I'm using pxResults property on a page of Code-Pega-List class.
The data for pxResults property is prepared by the activity that is called when the "Search" button is clicked on the same section. This activity uses Report Definition to retrieve all the necessary data from Pega database according to search criteria. Till this point everything works just fine. But... My Report Definition retrieves data not only from case instances but also from associated instances of Assign-Worklist and Index-* (there in an index optimizing some properties from embedded pages of a case for reporting) classes. Refer to screenshots below for details.
This data, obviously, is retrieved by means of joins on a class and declarative index, respectively. The data from joined classes is available in .pxPages page group on every page of pxResults page list.
The problem is that when I try to reference properties from joined classes on .pxPages I'm getting the following error saving section: String value of a cell: .pxPages(deal).DealDescription doesn't exist or is not a valid entry for this ruleset and its prerequisites
I've tried different ways of specifying .pxPages on Pages & Classes tab: .pxPages(deal) as shown on the picture, .pxPages(), SearchDealResult.pxResults().pxPages(deal) etc. None of them makes any difference - the error is the same.
After some experiments I've found out that this is a design-time error, not the runtime. I've found two workarounds to make this section be saved successfully:
- Create the property with the same name inside the work-class.
- Use Link control.
In both cases data is correctly retrieved from .pxPages when being referenced as .pxPages(<subscript>).<Property name>.
Does anybody know the (Pega-) way to solve the problem described?
Thanks in advance.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
US
Hi Alexander,
I remember running into the same exact issue a while back. I resolved it doing your first approach, saving pxPages as an imbedded page in my work class.
Thanks.
B.
Pegasystems Inc.
IN
Can you try specifying pxPages without subscript like : "SearchDealResult.pxResults().pxPages()"
Let me know if this helps. I have used pxPages from report definition in grid many times.
JCS Lanit - BPM
RU
Hi, Pankaj!
Thank you for your replay. Unfortunately the variant you've suggested doesn't work as well. As far as I remember this worked for PRPC 6.3.
Accepted Solution
Pegasystems Inc.
US
Hi Alexander,
I remember running into the same exact issue a while back. I resolved it doing your first approach, saving pxPages as an imbedded page in my work class.
Thanks.
B.
Updated: 24 Aug 2015 11:55 EDT
JCS Lanit - BPM
RU
Hi Brendan,
Thank you for your reply, but this approach is still a workaround that makes data model more complicated. I still hope to find a better approach.
Best regards,
Alex.
Evonsys (Pvt) Ltd
LK
In the section of pages and classes add page name as .pxPages(<subscript>) and add class name of the pxpages(<subscript>).
You can able to access the property like .pxPages(<subscript>).Propertyname
April Technologie
FR
In my case (PEGA 7.1.8), the solution describes by NadarajahN works fine. But, we have to check in the report definition before try to add the column in your section.
Tetco
SA
Thank you guys, this post really helped in resolving the issue and made to think in different way. Using Link Control option works fine and it's great, but the link format we have to modify in skin to make it exact to the other grid columns.
So the other options i tried using lablel control and i created a field value in the field value i referenced the property value {.pxPages().PropertyValue}.. It worked for me.
NCS Pte. Ltd.
SG
Hi Alexander,
I feel this issue could be resolved by defining .pxPages in Pages and Classes as .pxPages() to the required class without reference to any subscript value.
While referring the value in grid, please use .pxPages(PageName).PropertyName.
Hope this is helpful.
Thanks.
