MailMerge: Starting Each Merge Block on a New Page
Merge blocks in TX Text Control repeat based on matching data rows. Applying ParagraphFormat.PageBreakBefore to the first paragraph of a block forces each repetition onto a new page. Section breaks and column breaks within blocks provide additional layout control for merged documents.

A merge block is repeated based on the number of matching data rows in the hierarchical data object. The complete merge block is cloned and inserted under the original location in the template. But thanks to the flexibility of the "Flow Type Layout Reporting" approach, a merge block may contain everything: A table row, a complete table, text frames and paragraphs including all paragraph settings.
And these paragraph settings can be used to realize sophisticated layouts. The property ParagraphFormat.PageBreakBefore defines whether or not a paragraph is always rendered at the top of a page. If you apply this paragraph setting to the first paragraph of a merge block, the whole merge block begins at the top of a new page:
In the merged document, each of these block rows start at the top of a new page:
If the merge block should break after the first block and the new block should be rendered on a new section, a section break can be included into the merge block. Therefore, simply set the input position to the end of the block and select Breaks -> Next Page from the Page Setup group in the Page Layout ribbon tab.
This can be done with page breaks, continuous section breaks or column breaks to realize different layouts.
Cloud
Are we moving to the cloud? This question is changing from "if" to "when" and "how". Text Control ReportingCloud brings complete reporting functionality to the cloud so all developers can use it, irrespective of the platform or language they're using. Its highly RESTful API can be used to merge Microsoft Word compatible templates with JSON data from all clients including .NET, Javascript, PHP, Node.JS, jQuery, Ruby, Python, Android, Java and iOS.
Related Posts
ReportingCloud: Uploading Templates Vs. Sending Templates Inside MergeBody
ReportingCloud offers two template delivery methods: uploading to persistent storage via the /templates/upload endpoint, or embedding Base64-encoded template data in the MergeBody POST request.…
MailMerge: Table Headers and Repeating Blocks
Repeating table headers appear at the top of each page when tables span multiple pages during a MailMerge process. When combining table headers with nested merge blocks, the complete table must be…
ReportingCloud: Conditional Text Blocks Based on Merge Blocks
Conditional text rendering in ReportingCloud uses merge blocks combined with the RemoveEmptyBlocks setting. When the data source provides an empty object for a named block and RemoveEmptyBlocks is…
Web API Test Sandbox Released on ReportingCloud Portal
The ReportingCloud portal includes a Web API Test Sandbox for running endpoint calls against your own account data and template storage without affecting document quota. Each endpoint in the Web…
ReportingCloud: New Test Parameter for Document Quota Related Endpoints
ReportingCloud merge, convert, and findandreplace endpoints now accept an optional test parameter. Test calls bypass the document quota and produce watermarked output with a TEST MODE label,…
