Page Break On Table Group

[Phil]

Hi,

I have a report with a table in the detail section.  The table is grouped on a field called 'Organization'.  I also have a parameter called 'Organization'.  The table will give one full iteration for each organization that the user chooses in the organization parameter dropdown.

What I want is to page break after each iteration of the table.  So if I choose org1, org2 and org3 from the 'Organization' dropdown, the report will generate 3 pages, each with a table iteration for each organization that the user has chosen.

I need this functionality for a client by next week and I cannot figure out how this is done.  Can someone PLEASE help?

 Thanks,

Phillip

[Nasko]

Hello Phillip,

You need to configure the PageBreak property of the report section which contains the Table item (Detail or Group Header/Footer) e.g.:

PageBreak = After

This property can be configured in the report designer's Properties window after you select the appropriate report section.

Regards,
Nasko
Telerik

[Phil]

The PageBreak property only works for report groups.  That way, each table iteration is still on the same page, then there is a break afterwards.

I need to break after each iteration of the table group, not report group.  Is there any way to do this?

[Phil]

To clarify, when I say 'table groups' I meant to say 'row groups' within the table.

[Nasko]

Hello Phillip,

You are correct that the PageBreak property is available only for the report sections. It is not possible to place a page break between the Table rows/group iterations.

Regards,
Nasko
Telerik

[Kuruparan]

Hi Nasko,

I've been working on improving the response time of few WPF Telerik reports in our application. Noticed that applying pagination(Print Preview) considerably improved that performance. Is this the same case for Page break as well? Can I expect performance gain with page breaks?

[Nasko]

Hi Kuruparan,

The reporting engine in WPF renders the report with WPF primitives which are then displayed in the WPF report viewer. When there is a huge amount of those primitives on a single page (very large reports) you might experience delay when interacting with the WPF application.

In print preview the report is split based on the physical page size which is small enough so you don't see any performance issues when working with the same report.

If you use page breaks to split the report in reasonably sized parts I believe you will observe the same performance gain as seen with print preview.

Regards,
Nasko
Progress Telerik