Docx files with section break not working

Hi,
I want to convert an docx file which has several section break(next page) into pdf. But the output generated has a bunch of errors in the bulletin numbers. I’ve attached the input files and the difference for your reference

Version used : 25.8.0

Thanks
Ramani Sankar
issue.zip (126.5 KB)

@rsv2

Summary
When a DOCX that contains “Section break (Next page)” elements is converted to PDF with Aspose.Words, the list or bullet numbering that should continue across the break can appear incorrect in the resulting PDF.

Why it happens

  • The layout engine may reset list numbering when a new section starts, even if the list in the source document is configured to continue across sections.
  • List numbering that depends on field updates may not be refreshed before the PDF is generated, leading to mismatched numbers after a section break.

What to do next

  1. Check the list settings in the source DOCX
  • Open the document in Microsoft Word.
  • Select the affected list and verify that it is set to Continue numbering (or Continue from previous list) rather than Restart after each section.
  • Save the file and try the conversion again.
  1. Provide a minimal reproducible example to Aspose support
  • Create a short DOCX (1–2 pages) that includes a list spanning at least two “Next page” section breaks and shows the numbering problem.
  • Include the exact code you use for conversion and the Aspose.Words version you are using.
  • Attach the sample DOCX and code when you open a support ticket so the issue can be investigated.
  1. If the problem persists, consider updating the document before conversion
  • Ensure that any fields that drive list numbering are updated in Word before saving the DOCX.
  • After loading the document in your code, you may call the generic updateFields method (if available in your SDK) to refresh field values before saving to PDF.
  1. Validate the output
  • Open the generated PDF and confirm whether the numbering now continues correctly across each section break.

If the issue remains after these steps, the most reliable path is to work with Aspose support, providing the reproducible sample so they can determine whether it is a bug in the specific version you are using.

Note: The above guidance is based on typical troubleshooting steps for list‑numbering issues in Aspose.Words. Specific API names or version‑specific fixes are not referenced because the available evidence does not contain that information.

:warning: I could not fully verify this explanation against the retrieved sources. Please double-check the behaviour in your environment and confirm the exact SDK/version.

I have checked the input files from my side and everything appears to be fine

@rsv2
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSNET-28878

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.