Hi @lingareddyd6529: Please find my views.

1. Data page and RD in different class: Please check why you need the Data page in a different class. If you can create the data page in the same class, your issue is resolved. Again, if you still need both the rules in different class, you can get the data from DataSource (temporary parameter page) page and can do the mapping using the response data transform. Please refer below.

Make sure you pass the parameter page to the response data transform from Data page (pass current parameter  page), define DataSource page as parameter (page type) and in pages and classes.

2. When the Data page and Report are in the same class, as you mentioned, the details of the joined class will be available in pxPages(Subscript mentioned in join). Ideally you can use the same in places where the Data page is used.

If you really need to add these join properties in pxResults, please note that you may need to create duplicate properties in the actual class to hold these values (this is not suggested). Still if you need to continue with this approach, Create a Data response tat transform (As your data page is list mode, this will create a data transform in Code-Pega-List class) -> Loop (for each page in ) .pxResults -> Set the newly created property ( which i mentioned as duplicate) and source as pxPages(EM).<Property> (here the EM referred is from your screenshot). So the data transform will be something like below. Note: in the loop you need to select "Also use each page as source context"

Suggestion: These are required only when you are doing complex data mapping. I strongly suggest to check the data structure and where the data pages are created. In common scenarios, these are not required.

Thanks