Aspose.Words’ support of Microsoft Word fields is being improved all the time. At the moment, Aspose.Words updates around 3/4 of all Microsoft Word fields that can be updated. We’re hoping to support all ‘updateable’ fields before long. In the meantime, I’d like to share what progress we have made recently and what fields we have added to the supported list. I will use the same categorization offered by Word and OOXML specs.
Date and Time
While updating DATE and TIME fields was supported from the very beginning (due to the simplicity of implementation), the remaining fields in this category stayed unsupported for a significant time. The fields are:
Recently we filled this gap so that Aspose.Words can now update all Date and Time fields.
Aspose.Words supports all Document Automation fields that it makes sense to update. Two of them, GOTOBUTTON and MACROBUTTON, are not updateable, but were improperly displayed when rendering to PDF or image or saving to a format like HTML. The latest release of Aspose.Words fixes this issue.
Like for the Date and Time category, we supported the evaluation of all Document Information fields that were overlooked earlier. So the following fields are updated in the latest release:
Index and Tables
We have been working hard on one of the most popular Microsoft Word fields – table of contents (TOC). At the moment, Document.UpdateFields() (or Field.Update()) produces identical or very close result to how it looks after pressing F9 in Microsoft Word. In particular, we have fine-tuned tab stop positions generated for TOC entries in the latest release. Still, there is much work to do for this field because it is probably the most complex one.
There are a few fields in this category whose update is not supported yet, but they are on our TODO list and will be handled in the near future.
We have added support for two complex mail merge fields – ADDRESSBLOCK and GREETINGLINE. These two behave like compound MERGEFIELDs, allowing you to compose (surprise!) an address block or greeting line, respectively:
Also, the SET field is now supported, which means you can use it to define bookmark values.
The SEQ field is now fully supported.