Page Level Summary for Table Groups Data
Environment
| Product | Progress® Telerik® Reporting |
Description
The requirement is to display a summary per page in a Page section for the data displayed in Table Groups. For example, the number and count of the pages taken by the Table Group.
Suggested Workarounds
The scope that may be provided in the PageExec and other Page Functions should be linked to a report item, for example, a TextBox. The Table Groups are not directly related to report items and that's why the page aggregates cannot be based on the Table Group scope. That said, you cannot provide the name of the Table Group as a scope for a Page Function. There are two approaches to work around this limitation.
You may replace the Table Groups with Report Groups. The Report groups are associated with a dedicated report item. For example, you may place the table in the Report Group Header section, and Bind its DataSource to the parent's DataSource, that would be the group data. The table will display the entire group data in the Table once. You may use the Report Group name in the scope of the Page Functions. Note that in the detail section of the group you may still display Group data. If this is not necessary, you may set its Visible property to False. A sample based on this approch may be found in the
PageAggregateFromTableWithReportGroup.trdpdemo report.The second approach is to keep the Table Grouping and introduce a Parent group to it. It needs to be grouped by the same Expression (e.g. field) as the original group. This parent group will generate a new report item that spans the entire group. You may use this new item's name in the scope of the Page Functions. You may delete the content of this item and make it very small. It should be visible in order for the Expression to consider it though. A sample based on this approch may be found in the
PageAggregateFromTableWithParentTableGroup.trdpdemo report.