Replace Fields with Static Text

Replacing fields is often required when you wish to save your document as a static copy. For example, when sending as an attachment in an e‑mail. Converting fields such as DATE or TIME to static text will allow the document to display the same date as when it was sent. Also, in some situations, you may need to remove the conditional IF fields from your document and replace them with the most recent text result instead. For example, converting the result of the IF field to static text so it will no longer dynamically change its value when fields in the document are updated.

The diagram below shows how the IF field is stored in a document:

  • the text is surrounded by the special field nodes – FieldStart and FieldEnd
  • the FieldSeparator node separates the text within the field into the field code and field result
  • the field code defines the general behavior of the field, while the field result retains the most recent result when this field is updated using Microsoft Word or Aspose.Words
  • the field result is what is stored in the field and displayed in the document when viewed

update-remove-a-field-aspose-words

The structure can also be seen below in hierarchical form using the demo project “DocumentExplorer”.

update-remove-a-field-aspose-words-2

Fields That Cannot be Replaced by Text

Replacing a field with static text does not work properly for some fields in a header or footer.

For example, trying to convert the PAGE field in a header or footer to static text will result in the same value being displayed on all pages. This is because headers and footers are repeated across multiple pages, and when they remain as fields, they are handled especially so they display the correct result for each page.

However, in the header, the PAGE field translates well to static run of text. This run of text will be evaluated as if it were the last page in the section, which will cause any PAGE field in the header to display the last page over all pages.

The following code example shows how to replace the field with its most recent result:

EXAMPLE

Convert Certain Field Types in Specific Document Parts

Since the ConvertFieldsToStaticText method accepts two parameters – the CompositeNode properties and the FieldType enumeration, it is possible to pass any composite node to this method. This allows fields to be converted to static text only in specific parts of the document.

For example, you can pass a Document object and convert fields of the specified type from the entire document to static text, or you can pass a Body object of a section and only convert the fields found in that body.

The FieldType enumeration passed to the ConvertFieldsToStaticText method specifies what type of fields should be convert to static text. Any other field type found in the document will remain unchanged.

The following code example shows how to select fields of a specific type – targetFieldType in a specific node – compositeNode and then convert them to static text:

The following code example shows how to convert all IF fields in a document to static text:

The following code example shows how to convert all PAGE fields in a Body of a document to static text:

The following code example shows how to convert all IF fields in the last paragraph to static text:


FAQ

  1. Q: How can I replace all fields in a document with their current results?
    A: Use the static method FieldsHelper.ConvertFieldsToStaticText and pass the Document object as the composite node together with FieldType.ANY. This walks the whole document and replaces every field with its latest result.

  2. Q: I only want to convert fields of a specific type, such as IF fields. How do I do that?
    A: Call FieldsHelper.ConvertFieldsToStaticText with the document (or a body/paragraph) and the desired FieldType enumeration value, e.g., FieldType.FIELD_IF. Only fields matching that type will be converted.

  3. Q: My fields span multiple paragraphs; the conversion does not work when I pass a Paragraph node.
    A: When a field crosses paragraph boundaries, pass the parent node (e.g., the containing Body or Section) instead of the individual paragraph. This ensures the whole field is processed.

  4. Q: After converting PAGE fields in a header, all pages show the same number. Why?
    A: Converting a PAGE field in a header replaces it with a static run that reflects the value on the last page of the section. To keep correct page numbers, avoid converting PAGE fields in headers/footers or handle them separately after conversion.

  5. Q: Can I convert fields only in a particular section of the document?
    A: Yes. Retrieve the Section object, then its Body, and pass that Body to ConvertFieldsToStaticText. Only fields inside that section will be affected.