Different Result between ReportDefinition and DataPage which have join class table mapping
Dear Pega Community,
i have a task to display a report table_histori_telepon join with table_data_pengerjaan. thus, i create a report definition which name is RDHasilTelepon. RDHasilTelepon have prefix DataPengerjaan with only including matching rows filter conditions.
and for my Query tab i designed like picture in the below :
when i run Report Definition RDHasilTelepon the result show all column exactly like i designed in Query Tab. check the this picture below :
my question is when i'm trying to create data page and run the data page why the result is all property in join table_data_pengerjaan is not shown. for the table_hasil_telepon property result is show in pxResults(1), pxResult(2), and pxResult(3) and then table_data_pengerjaan property table is show in pxPages(DataPengerjaan). why the result in Report Definition is diferent with Data Page?. what i have supose to do to use/access the property in pxPages(DataPengerjaan) and then i'm using it in my section?. thank you very much.
thank you very much Mr. nistr to response my question. but, how i can use and call pxPages property in my section?. i'm using my prefix.column_name based on my report definition but the property/column name is not shown in my section. i need your advice. thank you.
You should be able to define another entry in the "Pages and Classes" for pxPages. Please see the screenshot below.
Since UI is not my strength, I believe this PDN post will be useful for you - https://pdn.pega.com/using-report-definition-rule-data-source-grid-layo…
thank you Mr. Nistr for your help. my section runs very well. thank you very much
Your understanding is correct. Even when you execute the report definition directly, the pyReportContentPage clipboard page has the data of the main class in pxResults and of the joined class in pxPages. The same is true for DataPage sourcing its data from a report definition.
Since the class for pxResults is the main class (applies to class) of the report, it cannot have properties which maybe specific to the joined class. Thus pxPages would help where each page could be of a different class (joined class in this case) and have properties from it.