Currently you can only force a page break on the boundary between sections.

If you could make it possible to add additional detail sections then a page break could be forced (especially usefull when designing a multi page report for a single data data item.

Additionally it would allow certain sections to be turned on and off based on databinding.

So a report might end up being made up of

PAGE HEADER
DETAIL 1
DETAIL 2
PAGE FOOTER

Hello,

I have been looking into your requirement and the body of the Report is only continuous, meaning that you can achieve this look only for your first page if any of the bodies you are defining requires more than one page it is going to prevail. If it is the first body it is going to drive the second one to the last page.

Please let me know if you require any further clarification on the matter.

I'm not sure I understand.

What I want is the ability to force a page break to happen in my detail section, Ideally by creating an additional detail section.

For example if I have a report that I want two pages for every record I can do this.  If, because of a table running longer for example, the first section runs to two pages instead of just one this results in 3 pages.

The key element is I wish the page break to be enforced, especially if I cannot guarantee the page length at design time (e.g. I've used a table)

If you are using multiple sections it would allow a binding to be made on the visibility to turn it off and on as needed (eg presenting a different section depending on the data)

Hello again,

I have been looking into your last reply and there is no functionality to support multiple bodies. If you are having a table displayed in the body and it would exceed the length of a page the report will automatically create a new page and continue with the table rows there.

Please let me know if this answers your question and if not please provide us with some descriptive screenshots that can better illustrate your requirement.

I get that I cannot do it, I'm asking can this functionality be put into the next version?

Of course,

I am going to log a Feature Request on your behalf and get back to you with the reference number. Please keep in mind there is no gurantee that it is going ot be implemented in the next release since our product team chooses new feature requests for development based on popular feedback from our customer base.  Infragistics continues to monitor application development for all of our products, so as trends appear in requested features, we can plan accordingly.