Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Step page incorrect for focused table row using custom section

SA-92324

Summary



In the custom row section, the Step page is incorrect for a focused table row when using a table whose source is another report.


Error Messages



Not Applicable


Steps to Reproduce

  1. Add a custom section to display the row details in a report definition.
  2. In the section, add a dynamic table layout with another report as the source.
  3. Add a link as the table column.
  4. Configure an onClick to open a report definition to pass the required parameter value.
  5. Click the link. The grid's last row record is retrieved always instead of the current row index value.


Root Cause



This is a classical use case of a grid within a repeating structure. When a grid is sourced with a report definition, a unique Results page is created based on the section name (for example: SubSectionInnerSec). In this case, pgRepPgSubSectionInnerSecBB is the Results page. This grid is invoked in each row of the report definition. Hence, the last row data is populated in pgRepPgSubSectionInnerSecBB. Since the actions are triggered on this page, the last row data displays always because the ID is the last row ID.




Resolution



An enhancement request, FDBK-63020, is created for consideration by Pega Product Management.

As a local-change, configure a 'Custom Results page' in the dynamic grid.

Published January 17, 2020 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us