Here is the answer from the other thread:
"There is no longer need to use this approach, which was 2 years ago, when there was no other way to align items and handle non fixed number of rows coming from your datasource.
Now you can use the table item that was introduced in the Q1 release this year. The Table item
can display dynamic data by rows and/or columns that extends greatly the flexibility of the report.
The most important part of the Table item (the Table, the Crosstab and the List items are actually the same Table item with different initial settings) are the Row and Column group hierarchies. The groups in the RowGroups
hierarchy define rules how the rows of the Table will be repeated, while the groups in the ColumnGroups
hierarchy are responsible for the columns. So the leaf groups in the RowGroups (leaf group has no child groups
) defines the rows in the Table Body
while the leaf column groups define the columns of the Table Body.
Depending on the grouping criteria, we have:
- dynamic groups - have any Grouping expression, ex. group1.Grouping.Add(new Grouping("=Fields.Country")). For the dynamic groups, the corresponding row/column will repeat for every record of the grouped data.
- static groups - no grouping criteria at all. For the static groups the corresponding row/column is rendered only once.
- detail groups -have a single empty grouping, ex. group1.Grouping.Add(new Grouping()). Usually you have only one row -or- column detail group. For a detail group the corresponding row/column is repeated for every row of the Table's data source. You may think of the detail TableGroup as the Report's Detail section.
Since we have Row and Column group hierarchies this means that one group may contain one or more child groups and you may have one or more root groups.
Depending on the configuration you may create:
- a simple static grid for ordering items by rows/columns. Use only static groups for the rows and columns.
- regular (vertical) table - the data records are displayed by rows. Define one detail group for the Row hierarchy and static column groups to define the columns.
- master-detail table - define one or more levels of nested row groups and if needed add a detail group to the end: [County] - [City] - [Detail]
- horizontal table - the data records are rendered by columns. Define one detail column group and put some static row groups to define the Table Body's rows.
- cross table/pivot table - Define dynamic groups in both Rows and Columns hierarchies; use aggregates for the body cells.
As you can see the flexibility of the Telerik Reporting's Table item is significant compared to most of the similar components that usually offer only one of the mentioned configurations: only grid that render the data source records by rows or pivot/crosstables that require both row/column groups."
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items.