I am in front of a strange issue concerning pagination: one case where it is working and in the same home section another pagination is not working.
Here are some configs details for each case :
Pagination works well and displayed in buttom of table :
a report where the pagination is not enabled because we are using SUM in one column in the query, a subreport is called where the pagination is enabled
data page called this report via a data transform calling an activity
In home section, this data page is called as a source in table layout which is inside a dynamic layout where the pagination is enabled as well with the same number by page as in the RD (20 by page)
==> in the portal table, the pagination is well shown
================================
Pagination does not work :
a report where the pagination is enabled, a subreport is called where the pagination is enabled
data page called this report via a data transform calling an activity
in a section apart (independant from home section ), this data page is called as a source in table layout which is inside a dynamic layout where the pagination is enabled as well with the same number by page as in the RD (20 by page)
in home section, in a dynamic layout where pagination is enabled also, we called the section apart
==> in the portal table, the pagination is not shown
So we have a blocking problem that content is missing (only 20 records are shown)
@AmiraF34 It sounds like the issue with pagination not displaying in the separate section may stem from how the pagination settings are configured across different layers. First, ensure that pagination is consistently enabled not only in the main report and subreport but also within the data page and the dynamic layouts in both the home section and the separate section. Check that the data transform and activity used to call the data page aren’t inadvertently limiting the results to 20 records. Additionally, verify that the table layout in the separate section correctly references the pagination settings from the data page and that there are no conflicting settings or overrides in the separate section’s dynamic layout. It might also help to compare the working home section setup with the non-working separate section to identify any discrepancies in configurations. Ensure that any conditional logic or visibility rules aren’t hiding the pagination controls in the separate section. Lastly, review any custom scripts or styles that might affect the display of pagination in the portal table. By systematically checking these areas, you should be able to identify why pagination isn’t appearing and resolve the issue so all records are accessible with proper navigation.
Hello I checked those points, it seems good. But when you said the config of pagination in the data page ? I cannot see where could I confgure the pagination in the data page, I see the pagination option to configure only in RD and section (tablelayout).
For information we the “Optimize code” in the table layout is allowed for both cases where is working/and Not working
@AmiraF34 If you’ve verified that pagination settings are correct in the Report Definition and table layouts, but still face issues, the problem might lie in how the data page is being utilized. Although data pages themselves don’t have a direct pagination setting, they can influence pagination through the data they provide. Ensure that the data transform or activity calling the data page isn’t restricting the results to 20 records by using methods like FirstN or similar functions. Check that the separate section correctly references the data page without applying additional filters or limits. Also, verify that the dynamic layout in the separate section doesn’t have any conflicting settings that might override the pagination, such as visibility rules or conditional logic that hides pagination controls. Compare the configurations between the working home section and the non-working separate section to spot any subtle differences. Additionally, inspect any custom scripts or CSS that might be affecting the display of pagination controls in the separate section. Sometimes, enabling “Optimize code” can inadvertently impact how components render, so try disabling it temporarily to see if pagination appears. Finally, ensure that the user roles and permissions in the separate section allow full access to all records and pagination features. By carefully reviewing these aspects, you can identify and resolve the issue preventing pagination from displaying correctly in the separate section.
@AmiraF34 please find the below url for reference. Dpage sourced with Report definition can be used for pagination, because paging info gets passed to pyReportParam page.
@Anoop Krishna Yes, so I changed how the data page is sourced => RD instead of Data transform and I pu the logic in the activity called by Data transform in the response data transform. It is working fine.
It is worth to add I tried to run the datapage with directly the report definition (called before via an activity called by a data transform in the datapage), and it is working I mean the whole result when running the data page (before only 20 records) and the pagination in the portal table is with pagination. The issue that the activity does not contain any configuration of the report definition pagination or other maybe related thing to pagination.
