How to Fix Word REF Field Showing Wrong SEQ Number
Question details
The user needs to resolve an issue where cross-reference (REF) fields display incorrect progressive heading numbers.

- Product
- Microsoft Word
- Device & OS
- not provided
- Scenario
- Creating cross-references for document headings that use a combination of AutoNum and SEQ fields for numbering.
- Observed behavior
- The REF fields incorrectly display the number 1 instead of calculating the actual progressive sequence number.
Press Alt + F9 (or Option + F9 on Mac) to toggle field codes on in your document. This allows you to see the underlying field code formulas instead of the calculated values, making it easier to identify outdated AutoNum fields.
Replace Field Codes with Built-in Multilevel List Numbering
The most reliable way to handle heading numbering and cross-references is to use the native Multilevel List feature instead of manual field codes.
Relying on legacy AUTONUM fields often breaks modern cross-referencing capabilities. By migrating your headings to a standardized multilevel list, you eliminate syntax errors and ensure that Word can correctly index progressive references.
Highlight the headings in your document that are currently using the problematic field codes and delete the legacy field code syntax.
Navigate to the 'Home' tab on the ribbon, click the 'Multilevel List' dropdown icon, and select a numbering format that is explicitly linked to Heading styles (e.g., 1 Heading 1, 1.1 Heading 2).
Go to the 'Insert' tab, click 'Cross-reference', choose 'Heading' as the Reference type, select your target heading, and click 'Insert'.

Use Consistent SEQ Fields with Proper Switches
If you must use field codes, replace legacy AUTONUM entirely with SEQ fields utilizing sequence identifier switches.
Manage Headings and Cross-references Seamlessly in WPS Writer
WPS Writer simplifies document formatting by providing an intuitive interface for multilevel lists and cross-referencing. You can easily build complex document structures and references without having to memorize or write manual field codes.
- 1. Open your document in WPS: Launch WPS Writer, open your existing document, and highlight the text you want to use as a numbered heading.
- 2. Apply a Multilevel List: Go to the 'Home' tab and click on the 'Multilevel List' icon to apply standard heading numbering formats.
- 3. Prepare for the reference: Place your text cursor exactly where you want the cross-reference to appear in your paragraph.
- 4. Access the Reference tools: Navigate to the 'References' tab located on the top ribbon and click on 'Cross-reference'.
- 5. Insert the heading reference: Select 'Heading' as the reference type from the dropdown, choose the specific heading you need from the list, and click 'Insert'.

Frequently Asked Questions
Why do my Word REF fields all show the number 1?
This typically happens when the referenced headings are numbered using the outdated AUTONUM field code instead of consistent SEQ fields or the built-in Multilevel List tool. Because AUTONUM is a legacy feature, modern cross-reference tools fail to calculate the correct progressive sequence from it.
How do I view the field codes in my Word document?
You can view the underlying field codes by pressing Alt + F9 on Windows (or Option + F9 on Mac). This will reveal the formulas, such as { SEQ Heading1 }, instead of the calculated text. Press the same shortcut again to hide them.
What is the difference between AUTONUM and SEQ fields?
AUTONUM is an older legacy field from early versions of Word used for automatic numbering, offering limited flexibility and often breaking references. SEQ fields are the modern, versatile standard, allowing for multiple sequence identifiers and advanced formatting switches like numbering restarts.
How do I force all field codes to update their numbers at once?
Press Ctrl + A to select your entire document, then press F9 to refresh and update all fields. If you have fields located in headers or footers, you will need to double-click into those specific areas and press F9 there as well.




