Table of Contents getting updated during conversion without setting updateFields to true

GroupDocs.Conversion Product Family
,
1

Hello Team,

I am converting a Word document using GroupDocs.Conversion with version 25.3.1.

In the source Word document, the table of contents are not updated with correct page numbers. However, during conversion, the Table of Contents gets updated automatically in the output document.

This happens even without explicitly setting the WordProcessingLoadOptions.UpdateFields property

Could you please confirm:

  1. Is Table of Contents always updated by default during conversion?
  2. If yes, what is the functional purpose of WordProcessingLoadOptions.UpdateFields?

Please clarify whether this behavior is expected or a defect.

cc: @pankajgupta
TocTest.docx (20.0 KB)

TocTest.pdf (75.1 KB)

2

@ravi1994

You reported that Table of Contents fields in a Word document are being updated during conversion with GroupDocs.Conversion 25.3.1, even though WordProcessingLoadOptions.UpdateFields is not explicitly set to true. You’re asking whether this behavior is expected or a defect, and seeking clarification on the purpose of the UpdateFields property.

  1. Based on the available information, it is unclear whether Table of Contents fields are always updated by default during conversion in GroupDocs.Conversion 25.3.1. The behavior you describe — where fields are updated without explicitly setting UpdateFields to true — is a user-reported observation and requires confirmation from official documentation or source code analysis . This could be either an intended behavior or a potential defect.

  2. According to the GroupDocs.Conversion for Java documentation, the WordProcessingLoadOptions.UpdateFields property is designed to control whether fields in the loaded document are updated during the conversion process. When set to false (which is the default), fields should not be updated . Therefore, if fields are being updated despite this property being unset or set to false, it suggests an inconsistency or unexpected behavior.

If you’d like further investigation into this behavior, please consider providing a minimal reproducible example or sample code that demonstrates the issue. A support engineer will follow up in this thread if needed.

3

Hello @ravi1994 ,

Thank you for contacting us. As you described, I was able to reproduce the same behavior with the resulting document on my side and have forwarded it to our developers for analysis. As soon as I receive feedback from them, I will get back to you and address your questions.

4

Sure @evgen.efimov, Please let us know once you have any update