nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Dynamic page break before table

bar

Hi all,
 
I have a report with two tables on one page. Both tables display data based on two input parameters, namely the time interval given by the user. The final report should be rendered as A4 PDF. If the selected time interval is large, the fist table nearly fills the complete first page. The second table starts also on the first page, but only three rows of the table are displayed here. The rest of the second table is displayed on the second page.
 
However, I would like to have a minimal amout of rows of the second table on the first page (e.g. 5 rows). If so, the second table is allowed to start on the first page, else a page break should be inserted before the second table (so that the table starts on the next page).
 
 
Is there a way to specify such a minium amount of rows?

Solutions I thought about: 
I tried to count either the rows of the first or the second table and to set pageBrakeBefore="always" of the second table depending on the row count. This, however, was not possible, since pageBrakeBefore must be set in onCreate and counting is only possible within onRender.
Another oppotrunity is to use a script on the dataset. The dataset script would count the resulting rows. This count should be applicable in the table's onCreate method, but I have a lot of those tables and this script would require a lot of additional queries. Is there any other opportunity?

Find more posts tagged with

Comments

mwilliams

You should be able to count your rows in the onCreate, though, another option could be to create an aggregation in the first table that gives you the count of rows for the table. If the number of rows reaches a certain number, you can just set the pagebreakafter for the first table.

bar

Thanks for the quick reply. Aggergation does the job

Solving the example given above introduced two other problems:
 
The page break should be only visible inside pdf documents. If I insert this condition: reportContext.getOutputFormat() == "pdf" I succeed when rendering to pdf directly. If I use the web viewer (html) instead their is no page break (as desired). When I export from web viewer to pdf, however, the page break does not occurr. I found that this is most likely due to the seprated tasks of generating and rendering when using the web viewer. Is there any chance to get the page break for pdf and pdf export from the web viewer and no page break within the web viewer?
 
 
Assume the first table fills the first and a small part of the second page. Due to a high value of the aggregated count, a page break will be insterted after the first table. There is, however, enough space to print the second table on the second page as well.
I could introduce a more complex logic for page breaks, e.g., approximate how many rows I have per page so that I can compute how many rows will be on the page the first table ends. I have many different tables, doing this for each tabe is kind of annoying. Is there any way to influence the rendering engine directly?

mwilliams

I don't think you'll be able to influence the page breaks at render time, so exporting the content of the html report to PDF will just give you exactly what you created for the html output. Your best bet here will probably be to add a link to run the report in PDF and just run it from scratch and remove the toolbar export option. Most likely you'll have to do the manual counting and resetting your count in the onpagebreak event to know how many rows have happened on the given page to account for the first table barely running onto the second with enough room to start the second table.