Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.
Typically, a field inserted into Microsoft Word already contains an up to date value. For example, if the field is a formula or a page number, it will contain the correct calculated value for the given version of the document. But if you have an application that generates or modifies a document with fields like merging two documents or populating it with data, then ideally all fields must be updated for the document to be useful.
When a document is loaded, Aspose.Words mimics the behavior of Microsoft Word with the option to automatically update fields is switched off. The behavior can be summarized as follows:
TOC, when you need toTo explicitly update fields in the whole document, simply call the UpdateFields method. To update fields contained in part of a document, obtain a Range object and call the UpdateFields method. In Aspose.Words, you can obtain a Range for any node in the document tree, such as Section, HeaderFooter , Paragraph, etc. using the Node.Range property.You can update the result of a single field by calling the Update method.
When you execute conversion of a document to a fixed-page format e.g. to PDF or XPS, then Aspose.Words will automatically update page layout-related fields PAGE, PAGEREF found in headers/footers of the document. This behavior mimics the behavior of Microsoft Word when printing a document.
If you want to update all other fields in the document, then you need to call UpdateFields before rendering the document.
The following code example shows how to update all fields before rendering a document:
When you execute a mail merge, all fields in the document will be automatically updated. This is because the Mail Merge is a case of a field update. The program encounters a Mail Merge field and needs to update its result, which involves grabbing the value from the data source and inserting it into the field. The logic is of course more complicated, for example, when the end of the document/mail merge region is reached but there is still further data to be merged, then the region needs to be duplicated and the new set of fields updated.
You can use UpdateLastSavedTimeProperty property whether to update the corresponding built-in document property LastSavedTime when saving the document.
The following code example shows how to update this property:
Q: How can I update all fields in a document using C++?
A: Load the document, call Document::UpdateFields(), and then save the document. This updates every field, including TOC, page numbers, and formula fields.
Q: How do I update fields only in a specific part of a document, such as a header or a section?
A: Obtain the Range of the target node (e.g., HeaderFooter* header = ...; Range* range = header->get_Range();) and call range->UpdateFields(). Only fields inside that range are refreshed.
Q: Are page‑related fields like PAGE and PAGEREF updated automatically when converting to PDF or XPS?
A: Yes. During rendering to fixed‑page formats, Aspose.Words automatically updates page‑related fields in headers and footers. For other fields you must call UpdateFields() before rendering.
Q: Does Mail Merge automatically update fields, or must I call UpdateFields() after a merge?
A: Mail Merge automatically updates all fields that are part of the merge operation. No additional call to UpdateFields() is required unless you have other fields that need refreshing.
Q: How can I ensure the LastSavedTime built‑in property reflects the current time when saving?
A: Set SaveOptions::UpdateLastSavedTimeProperty to true before saving the document. This updates the LastSavedTime property to the current system time.
Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.