Use a marker that makes stale data obvious
Choose a fictional value such as CHECK-A42 for a single field and leave the rest of the test record unchanged. If the old sample still appears, you have learned something useful: the file is not reflecting that intended value. Do not begin by rewriting every mapping or introducing a fallback.
Record the input version, template version and exact file you inspected. Looking at yesterday’s download is an easy way to mistake a correct change for a failure. Keep the original business record untouched while tracing the synthetic case.
Follow the value through four boundaries
| Boundary | Question | Evidence to retain |
|---|---|---|
| Source | Does the intended record actually contain the field? | Non-sensitive fixture showing its spelling and type |
| Mapping | Does the outgoing object preserve that field? | Redacted structural record, not a credential-bearing request |
| Binding | Does the component address the right object or row? | Template expression and expected location |
| Layout | Is the value present but hidden, clipped or off-page? | Complete output and the exact affected region |
A value absent at the first boundary is not a template rendering problem. If it disappears in the connector, editing the PDF component only hides the real fault. Change one boundary at a time and compare the same fixture.
Distinguish a root field from a row field
In our sample, report_id belongs to the whole report while status belongs to each member of items. A repeating component needs the current row’s status; a top-level reference can legitimately repeat the same value. Compare against A01 / Complete and B02 / Pending, not two identical placeholders.
Use the documented Normal Section scope or table cell configuration for the component you actually chose. A syntactically valid expression can still address the wrong semantic field.
For a Word-template alternative, DocuGenerate documents empty output for unmatched tags. That makes exact field matching important; a blank is not evidence that a required source value was intentionally absent.
Use the observed symptom to choose the next check
| Symptom | Investigate next |
|---|---|
| All fields show the earlier sample | Input supplied to this generation and the file version |
| Only one field is blank | Spelling, nesting, type and component binding |
| Every row shows the first task | Current-row reference and array binding |
| Text begins correctly but ends early | Container size, wrapping and pagination |
| Blank appears only when the note is absent | The declared empty-state and conditional layout |
These are diagnostic hypotheses, not guaranteed causes. Save what the check showed. Do not fill a missing business status with Complete or suppress a required warning to eliminate the symptom.
Retain the smallest failing case
Reduce the example to the field and surrounding structure necessary to reproduce the issue. Keep an otherwise identical passing case. The pair helps a maintainer understand the difference without handling private client material.
After repair, restore the full synthetic pack and check the related rows and page boundary. A corrected label in one file does not prove the mapping is safe for missing, empty or long values. Record the actual result and leave unresolved output held.
Sources and evidence limits
Documentation checked 2 October 2026. Worked examples are fictional; these are not hands-on merchant test results.
- The design workflow — checked 2026-10-02
- Data-binding for Normal Sections — checked 2026-10-02
- Simple Table Component — checked 2026-10-02
- DocuGenerate merge-tag behavior — checked 2026-10-02