Here's the layout
_______________________
[Page Header]
--------------------------------------
[HeaderData]
[HeaderDetails]
[Table1]
[SubReport1]
[SubReport2]
[SubReport3]
--------------------------------------- -> PageBreak.After
[PageFooter]
_________________________
------ Denotes the DetailSection wrapper. The DetailSection also has KeepTogether = True
____ Denotes the page edges
Now what is current happening is one set of data exceeds the the size of a single page - and instead of honoring the page break and just starting the data on the next page and followed by another page which would have another page break and be mostly whitespace. It's placing the data on the page before.
Example:
_____________________
[Page Header]
--------------------------------------
[HeaderData]
[HeaderDetails]
[Table1]
[SubReport1]
[SubReport2]
[SubReport3]
--------------------------------------- -> PageBreak.After
[HeaderData2]
[HeaderDetails2]
[Starts the table1 data for the next page . . . continued on the following]
--------------------------------------- -> continued on the next page
[PageFooter]
___________________________
I know that part of the issue is that the data of the second data set is larger it needs an additional page (But not two complete pages). However, the render should still respect the page break from the page prior and just include an extra page after - not bleed onto the page before.
The page break is functioning - if the data sets are small enough to fit two to the same page, it does not. (This report inherits from another report - with the page break being set using an inherited method that is called on this report, but not on the parent. This report also has one of the subreports visible while the other does not - which also adds to the height issue in question. [I also hid this on the inherited report so the sole difference was the page break to confirm the page break worked.])
The closest I got to finding a similar reported issue were Daniel's comments here: https://www.telerik.com/forums/how-to-not-keeptogether-a-subreport
3 Answers, 1 is accepted
Please check my reply the support ticket you opened on the same topic.
Regards,
Silviya
Progress Telerik
Rank 1
I've attached an image file for those who need a clearer representation of the behavior I'm seeing. I've been directed to create a feature request as the current behavior has been denoted as a "feature", not a bug from the support rep.
The feedback link can be found below:
https://feedback.telerik.com/Project/162/Feedback/Details/239644-keeptogether-should-honor-page-breaks
As we discussed in support ticket #1144729, the case is under investigation. There is indeed an issue with paging mechanism which is reproducible with the project you provided.
The project is currently under investigation by our development team. We will update you in the support ticket about the results of the investigation.
Regards,
Katia
Progress Telerik