Share via

Numbered List/Clause Numbers Disappear When Document Compatibility Mode is Upgraded

G, Girish (TR Technology) 0 Reputation points
2026-05-06T05:33:56.6033333+00:00

We are experiencing an issue where numbered clause headings (e.g. ARTICLE I, Section 1.01, 1. Interpretation) disappear when documents are opened in newer versions of Microsoft Word or when the compatibility mode is automatically upgraded.

Environment:

  • Documents are server-generated .docx files using Aspose.Words (License Version 3.0)
  • Template: GentTemplate_USStandardDocument.dotm with compatibilityMode val="14" (Word 2010)
  • Affected users are running Word 2019 / Microsoft 365

What Happens:

  • Server generates .docx with compatibilityMode val="14" (Word 2010)
  • User opens the document in Word 2019 / Microsoft 365
  • Word automatically upgrades the compatibility mode to val="15" or val="16", or removes the setting entirely
  • Upon upgrade, numbered clause headings disappear completely — the text remains but the numbers are gone
  • This affects styles such as TitleClause, LFTitle-Clause, LFParasubclause1 which rely on list numbering defined in numbering.xmlWe are experiencing an issue where numbered clause headings (e.g. ARTICLE I, Section 1.01, 1. Interpretation) disappear when documents are opened in newer versions of Microsoft Word or when the compatibility mode is automatically upgraded. Environment:
    • Documents are server-generated .docx files using Aspose.Words (License Version 3.0)
    • Template: GentTemplate_USStandardDocument.dotm with compatibilityMode val="14" (Word 2010)
    • Affected users are running Word 2019 / Microsoft 365
    What Happens:
    • Server generates .docx with compatibilityMode val="14" (Word 2010)
    • User opens the document in Word 2019 / Microsoft 365
    • Word automatically upgrades the compatibility mode to val="15" or val="16", or removes the setting entirely
    • Upon upgrade, numbered clause headings disappear completely — the text remains but the numbers are gone
    • This affects styles such as TitleClause, LFTitle-Clause, LFParasubclause1 which rely on list numbering defined in numbering.xml
Microsoft 365 and Office | Word | For business | Windows
0 comments No comments

3 answers

Sort by: Most helpful
  1. Nam-D 3,855 Reputation points Microsoft External Staff Moderator
    2026-05-06T07:36:37.9733333+00:00

    Hello @G, Girish (TR Technology),

    I understand you having issue when a document is created with compatibilityMode val="14" (Word 2010) and then opened in Word 2019 or Microsoft 365, Word automatically upgrade the compatibility mode to a newer version or remove the compatibility flag entirely.  

    As a next step, please try opening the document in Word on the web (Word Online) and check whether the numbering issue still occurs there, as this can help determine whether the problem is specific to the desktop client or related to the document structure itself. 

    Currently, Office 2010 is now out of support, I cannot investigate this behavior further on that compatibility level. My recommendation is to update the document template and generation process to target a newer, supported version of Microsoft Word so that you can receive full, up to date support going forward. 

    I understand this is disruptive, especially in environments with strict document formatting requirements, but the change in behavior is tied to Word’s evolution rather than an error that can be corrected on the Microsoft client side. 

    Note: Please understand that as a forum moderator, my primary goal is to provide helpful guidance and support through general troubleshooting steps. While I don’t have access to internal systems or test devices required to resolve backend/account issues, I truly appreciate your understanding of these limitations.  

    I hope you find this information helpful. If anything is unclear, please don’t hesitate to reach out to me. 

    0 comments No comments

  2. G, Girish (TR Technology) 0 Reputation points
    2026-05-06T05:45:00.8566667+00:00

    Below are the version used from our end.

    Detail Value
    Product Microsoft Word for Microsoft 365
    -------- --------
    Product Microsoft Word for Microsoft 365
    Version 2603 (March 2026)
    Build 16.0.19822.20086
    Architecture 64-bit
    Channel Current Channel
    0 comments No comments

  3. Q&A Assist
    2026-05-06T05:34:19.68+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The described behavior matches a known Word issue where heading or clause numbering disappears under certain conditions in newer Word builds.

    From the available information, there are two relevant Word issues:

    1. Heading numbering disappears when a Style Separator is used
      • After upgrading to Word version 2512 (build 16.0.19530) or later, heading numbering can disappear when a Style Separator is present.
      • Status is FIXED via a service change.
      • For users still seeing the issue, all Office apps must be closed and Word reopened so the service change is picked up.
      • This fix is reported as present from at least Release 2602.
    2. General multilevel numbering/list issues in Word
      • There are known issues where multilevel numbered lists change or lose numbering when pasted or when list definitions are unstable.
      • Workarounds include manually renumbering or re‑defining the multilevel list, and ensuring numbering is set up using the recommended multilevel numbering approach.

    Given the environment (Word 2019 / Microsoft 365) and the fact that numbering disappears when compatibility mode is upgraded, the most relevant Microsoft guidance is:

    1. Check whether the Style Separator issue applies
      • If the clause styles (for example, TitleClause, LFTitle-Clause, LFParasubclause1) use Style Separators to keep numbering and text on the same line, the disappearing numbers may be the same bug described in “Heading numbering disappears after applying Style Separator in Word.”
      • Ensure affected clients are on a build that includes the fix (at least Release 2602) and that users have fully restarted Office (close all Office apps, then reopen Word).
      • If numbering returns after updating and restarting, the issue was the Style Separator bug.
    2. If numbering is still unstable, treat it as a multilevel numbering problem
      • Word has documented issues where multilevel numbered lists change when content is moved or when list definitions are not fully stable.
      • In such cases, Microsoft’s guidance is to:
        • Re‑establish the multilevel numbering in the template using the recommended multilevel numbering setup (for example, as described in the referenced Word numbering best‑practice articles in the Q&A).
        • If a specific list instance is broken, manually renumber affected items as a workaround (select the item, press Backspace, type the correct number/letter, then press Tab). This can have knock‑on effects further down the list, so continue down the list correcting as needed.
    3. Compatibility mode considerations
      • Word uses Compatibility Mode to preserve layout and disable newer features when opening documents created in older versions.
      • When a document created in an older mode (for example, Word 2010 compatibility) is opened in newer Word versions, Word may upgrade the compatibility mode.
      • Conversion to a newer format can change how certain features (including numbering) behave. If the numbering definitions in numbering.xml rely on behaviors specific to the older compatibility mode, upgrading can expose latent issues in the numbering setup.
      • If the numbering is stable only in the older compatibility mode, consider:
        • Keeping documents in the older compatibility mode for now (do not convert to the newer format) while testing and updating the template’s numbering definitions.
        • Once the template’s multilevel numbering is rebuilt following best practices, regenerate documents and test again in the newer compatibility mode.
    4. If the problem persists after updating Word and restarting
      • Confirm that affected clients are on a build that includes the Style Separator fix (Release 2602 or later).
      • If numbering still disappears when compatibility mode is upgraded, treat this as a template/list‑definition issue and rebuild the multilevel numbering in the template following the stable numbering guidance referenced in the Q&A posts.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.