There is already Declare Index for the .pyWorkParty() page and "Index class to write" is index-WorkPartyUri. So that you can get the work party details in report by joining with index-WorkPartyUri class, Joining condition could be the pxInsIndexedKey of index-WorkPartyUri class and pzInsKey of Your Work Class.
I tried to join Index-WorkPartyUri class in our reports and it works very well.Thank you very much for the suggestion.
But there is an another issue is that, actually, in order to show the WorkParty Operator's Department information on reports, we added a Single Page property called "OperatorID" in Data-Party class, which Page definition is Data-Admin-Operator-ID. And get the data through .pyWorkParty().OperatorID.pyDepartment. I think it is also needed to add this property in Index-WorkPartyUri class and expose it to column perhaps. But PRPC is not allowing to expose property in Index-WorkPartyUri class by Property Optimization For Report.
Is it possible to expose this department property maually, or has any other way to solve this inssue?
I resolved this issue by exposing Data-Admin-Operator-ID.pyDepartment property to DB (Since this class is a Pega shipped class and Pega also not allowing to expose property, I alter PR_OPERATORS table manually by adding column with same name "PYDEPARTMENT" and resaved DB-Table instance , as a result it works well ).And then joined Data-Admin-Operator-ID class to our RD. Now reports get Department data from PR_OPERATORS table PYDEPARTMENT column instand of BLOB, and report performance is been improved
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
We have also sent you a private message opening up a communication channel in case you have any further questions.