By allentatakai
Prepare the input
Inspect field names as stored in the document. Printed labels beside a field may differ from the identifier expected by an automation command.
These examples use local sample filenames. Substitute your own paths and check jetformat word form-fields --help against the installed version before running the task. Put paths containing spaces inside quotes.
Run the command
jetformat word form-fields contract.docxInspect the field inventory before building --set arguments for word fill-fields. Matching visible labels is not sufficient when the internal field name differs.
Review before the next step
Compare required identifiers with the incoming data mapping. If no legacy fields are listed, investigate the template structure before assuming it is an empty form.
Copy the exact field name into the filling command; if no fields appear, check whether the template uses content controls instead.
Keep the workflow repeatable
This is a free utility or read operation. It does not need a paid conversion to inspect the result.
Run jetformat word form-fields --help to compare options with your installed version.
See the word command reference for the surrounding workflow.
Keep the input revision with the result so a later reviewer can reproduce the decision. For a write operation, choose a new output path first; use overwrite flags only when replacing a previously reviewed result is intentional.
See the word form-fields options and examples for the command reference. Browse related word commands when the next step requires a different operation.