Display tables in one page, print in several

[ANDREY]

Hello,

In reports, that I need, there are some tables that should be displayed (in interactive mode) in one page but printed in several pages. To prevent page split in the interactive mode I try to make one big table with subtables (I merge cells and then insert panel+table) and then injust KeepTogether property to control the page break places. However, sometimes it is not work as I suppose, and also it doesn't allow me to print small tables (that fit in one page) on different pages.  

Are there better solutions for my need? Is there any way I can clearly define the strict page break place?  

Thanks!

Reports are made in standalone designer, and then shown in html5 report viewer.

[Silviya]

Hi Andrey,

You can achieve the desired behavior by creating each Table in separate static groupHeaderSection and set a binding rule which will put PageBreak only in PrintPreview mode (using RenderingFormat object). For example:

Property Path: PageBreak
Expression: = IIf(RenderingFormat.Name = 'IMAGEInteractive', 'None', 'After')

This would work for reports in the designers, but in case you are using the HTML5 Report Viewer Interactive mode only the Rendering Format should be changed to HTML5Interactive. For more information, check Rendering Extensions.
I'm attaching a sample report definition for reference.

Regards,
Silviya
Progress Telerik

[ANDREY]

Thanks for the answer! 

However, If the tables are quite big this approach will put them on different pages in the interactive mode even if all PageBreak properties are set to None.

[ANDREY]

I'll duplicate it just in case.

Silviya, thanks for the answer!

However, If the tables are quite big this approach will put them on different pages in the interactive mode even if all PageBreak properties are set to None.

[Silviya]

Hello Andrey,

This is expected behavior due to the paging mechanism of the Interactive View called soft page breaks, where the report is optimized for screen-based viewing and delivery.
However, a possible workaround is to create a User function which will set report's PageSettings.PaperSize.Height to a larger value.

Regards,
Silviya
Progress Telerik