logo
search
Formatting Issues

How to Fix Word Index Subentries Displaying on Separate Rows

Muhammad TalhaMuhammad Talha Sep 27, 2026 869 views

Question details

The user needs to correct an issue where index subentries are improperly split onto separate rows instead of nesting under their parent entries.

How to Fix Word Index Subentries Displaying on Separate Rows
Product
Word Processing Software
Device & OS
not provided
Scenario
Updating or generating a document index containing main entries and multiple subentries.
Observed behavior
Index subentries appear on isolated rows in the generated index, typically caused by manually edited, inconsistent XE field codes or disruptive section breaks.
Before you start

Enable formatting marks by going to the Home tab and clicking the Show/Hide paragraph icon (¶) so you can clearly see hidden XE field codes, section breaks, and paragraph returns.

Solution 1Recommended

Correct Inconsistent XE Field Codes

Identify and rebuild poorly formatted index entries to ensure subentries group properly under a single main index entry.

Inconsistent spacing, capitalization, or syntax in manually typed XE (Index Entry) fields often prevents subentries from nesting properly. Recreating them with the built-in tool ensures accurate formatting.

1
Display Field Codes

Press Alt+F9 on your keyboard to reveal all hidden field codes in your document, including the XE fields used for the index.

2
Locate Inconsistent Entries

Find the affected main entry and its subentries within the text. Look for inconsistencies in the pattern. A correct pattern should look like { XE "Australia:Noosa" }.

3
Delete and Recreate Entries

Delete the problematic, manually edited XE fields. Instead of editing the codes by hand, highlight the text and use the 'Mark Index Entry' feature to correctly generate new fields.

4
Update the Index

Scroll to your index, click anywhere inside it to select it, and press F9 to update the fields and apply the corrected layout.

Correct Inconsistent XE Field Codes
Avoid Manual Edits: Manually typing or altering XE field codes frequently leads to syntax errors. Always use the built-in Mark Index Entry dialog to add or modify index items.
Manage Indexes Easily

Create and Manage Document Indexes with WPS Writer

WPS Writer offers an intuitive and reliable way to manage complex document elements like indexes, tables of contents, and field codes. You can easily mark index entries and seamlessly update your document layouts without worrying about field code glitches.

  1. 1. Open Your Document: Launch WPS Writer and open the document where you need to build or troubleshoot an index.
  2. 2. Mark Index Entries: Navigate to the References tab and click 'Mark Entry' to accurately tag your index items with proper subentry nesting.
  3. 3. Insert and Update Index: Insert your index from the References tab. To apply fixes, simply right-click the index block and select 'Update Field'.
Fully compatible with Microsoft Word document formats (.docx and .doc)Intuitive 'Mark Index Entry' tool to prevent manual field code syntax errorsEasily toggle field codes using standard shortcuts like Alt+F9 for quick troubleshootingLightweight architecture ensures fast performance even with massive, heavily indexed documents
microsoft office alternative - wps office

Frequently Asked Questions

What are XE fields in a document?

XE (Index Entry) fields are hidden field codes used to mark specific text strings for inclusion in a generated index. They define how the entry will ultimately appear, dictating the structure of main entries and subentries.

How do I show or hide field codes while editing?

You can toggle the display of field codes by pressing Alt+F9 on your keyboard. This reveals the raw code, such as the XE tags, allowing you to identify syntax errors or inconsistencies.

Why does updating my index with F9 not fix the separated rows?

If pressing F9 doesn't fix the issue, the underlying XE field codes are likely typed inconsistently (e.g., mismatched spacing or capitalization) or a hidden section break is interfering. You must locate the incorrect XE field, delete it, and recreate it.

What is the correct syntax for a main entry and a subentry?

A subentry is separated from its main entry by a colon within the field code. For example, { XE "Australia:Noosa" } indicates that 'Australia' is the main entry and 'Noosa' is its nested subentry.