Skip to main content
Windward

Limitations on Word FIELD Support

Overview

The below limitations are as of the lastest version. Support for forms, some formatting, etc.may only be available in the latest version. Only part of the below functionality is implemented for RTF.

  • We ignore formatting within the field results (basically we always do \* MERGEFORMAT).
  • We ignore formulas.
  • calcOnExit(), entryMacro(), and exitMacro() are not applicable for report generation.

 

For fields we pass blindly across, like DATE or NUMCHARS, any formatting should appear in the generated report.

 

However, for fields where we calculate the result such as PRINTDATE and PAGE, the formatting is limited as follows:

  • We only handle the general formats: ALPHABETIC, alphabetic, Arabic, Roman, & roman.
  • Numeric and date formats such as "00.00" and "mm-dd-yyyy" are passed to the Java classes DecimalFormat or SimpleDateFormat. These are about 98% identical, but there are some differences.

 

 

Fields written as based on the report content

We write the following fields based on the report content.

The form fields FORMCHECKBOX, FORMDROPDOWN, and FORMTEXT are written as forms to DOCX, PDF, and HTML output. For other formats they are written as text.

FORMCHECKBOX Written as forms to DOCX, PDF, and HTML output. For other formats this is written as text.
FORMDROPDOWN Written as forms to DOCX, PDF, and HTML output. For other formats this is written as text.
FORMTEXT Written as forms to DOCX, PDF, and HTML output. For other formats this is written as text.
HYPERLINK Converted to standard hyperlink.
INDEX Uses very few of the configuration settings.
KEYWORDS Will use the value from Report.Keywords if set. If not set, it will use the value in the template properties.
NUMPAGES Only use number formatting codes listed above.
PAGE Only use number formatting codes listed above.
PAGEREF Ignores the \p setting.
PRINTDATE The date/time the report is generated.
REF Converted to standard hyperlink.
SECTION Only use number formatting codes listed above.
SECTIONPAGES Only use number formatting codes listed above.
SUBJECT Will use the value from Report.Subject if set. If not set, it will use the value in the template properties.
SYMBOL Converted to the specified character.
TITLE Will use the value from Report.Title if set. If not set, it will use the value in the template properties.
TOC Ignores \a, \b, \c, \d, \f, \s, \u, \w, \x, & \z. For \n ignores the level range.
XE Only uses the \b, \i, & \t codes.

 

 

Fields written to DOCX reports, but not passed to other report output formats

The following fields are blindly written to DOCX reports but are not passed to any other report output formats:

Document Automation COMPARE, DOCVARIABLE, GOTOBUTTON, IF, MACROBUTTON, PRINT
Equations and Formulas =formula, ADVANCE, EQ
Index and Tables RD, TA, TC, TOA
Links and References INCLUDEPICTURE, INCLUDETEXT, LINK

 

 

Fields written to all output formats

The following fields are blindly written to all output formats. For formats other than DOCX the result text of the field is written.

 

Date and Time CREATEDATE, DATE, EDITTIME, SAVEDATE, TIME
Document Information AUTHOR, COMMENTS, DOCPROPERTY, FILENAME, FILESIZE*, INFO, LASTSAVEDBY, NUMCHARS*, NUMWORDS*, TEMPLATE
Links and References AUTOTEXT, AUTOTEXTLIST**, BIBLIOGRAPHY , CITATION, NOTEREF, QUOTE, STYLEREF
Mail Merge ADDRESSBLOCK, ASK, BARCODE, COMPARE, DATABASE, FILLIN, GREETINGLINE, IF, MERGEFIELD, MERGEREC, MERGESEQ, NEXT, NEXTIF, SET, SKIPIF
Numbering AUTONUM, AUTONUMLGL, AUTONUMOUT, LISTNUM, REVNUM

* FILESIZE, NUMCHARS, and NUMWORDS should logically be the values of the generated report. However, calculating these is expensive and no one needs them so for performance reasons, these will be the values for the template, not the report.

** AUTOTEXTLIST is normally used for Windward tags. But if it does not contain a tag, then it is passed across blindly.

  • Was this article helpful?