What actually works (recommended solutions)
Solution 1: One certificate per section (most reliable)
Instead of repeating rows on the same document flow:
- Create a Section Break (Next Page) immediately after your certificate layout
- Place the repeating section inside the section
- Ensure each iteration lives in its own document section
This forces Word to:
- Reset margins
- Reset headers and footers
- Reset vertical layout position
This is the only true reset mechanism Word respects.
Solution 2: Repeat sections, not table rows
Restructure your template so that:
- The repeating section wraps a container block
- The table is fully inside the repeating section
- The repeating control is not attached to a row
Preferred structure:
- Repeating Section
- Section Break (Next Page)
- Table
This dramatically reduces drift.
Solution 3: Fixed table height for the certificate
If every certificate is visually identical in height:
- Set the table row height to Exactly
- Ensure total height fits one page
This eliminates reflow calculation entirely.
This works best when:
- Images are consistent size
- No conditional content expands vertically
Solution 4: Generate one file per record, then merge
For high‑stakes documents like certificates:
- Generate one Word or PDF per record
- Merge afterward if needed
Many production systems use this pattern because it avoids all Word pagination edge cases.
Why this happens
1. Word does not “reset” layout per repetition
When Populate a Microsoft Word template expands a repeating section content control, Word treats the entire document as one continuous layout flow.
Each iteration:
- Re-evaluates table row height
- Re-applies paragraph spacing
- Re-applies internal table padding
- Recalculates anchored objects (logos, shapes)
Tiny rounding differences accumulate. By page two or three, those fractions add up, which is why you see:
- Top margin slowly increasing
- Bottom margin shrinking
- Content drifting down page by page
This is not visible when editing the template manually, only when rendered by the connector.
2. Repeating table rows are especially fragile
Wrapping a repeating section around a table row is the most problematic layout combination because:
- Word must dynamically calculate row height
- Images and shapes anchor slightly differently each time
- Table cell padding gets compounded
Even with:
- Inline wrapping
- No extra paragraph marks
- Page break before
- Fixed row height disabled
…the recalculation still happens.
3. Page breaks inside repeating controls are unreliable
A “Page break before” inside a repeating row or embedded control does not behave as a hard reset.
From Word’s perspective:
- It is still one flowing object
- The vertical cursor position is inherited
- Margins are not reinitialized
That is the core reason the drift compounds.
What does NOT fix it (you already found this)
You correctly ruled out all of the usual advice:
- Text wrapping None
- Allow row to break across pages
- Removing paragraph marks
- Design Mode off
- Page break before
None of these address the root problem.
Why Microsoft has never fully fixed this
The Word connector uses Word Online’s layout engine, not the desktop engine. That engine:
- Is optimized for collaboration, not print‑perfect pagination
- Does not guarantee deterministic layout for complex repeating structures
- Has known limitations with tables, images, and repeating content
This is not documented clearly, but it is longstanding behavior.
Bottom line
- There is no hidden setting you missed
- The drift is caused by cumulative layout recalculation
- Repeating table rows combined with pagination will always be brittle
- Section breaks or one‑record‑per‑document are the only dependable fixes
✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.
