How to Manually Map PDF and XFA Fields to Excel
A four-stage guided flow for mapping complex PDF and XFA forms — parent and child tables, validation rules, and review before generating.
Automatic mapping handles most PDFs well. But some forms fight back — XFA documents with hundreds of fields, cryptic internal names, or several related tables feeding one form. For those, ExForms has a guided manual mapping flow that walks you through it in stages. Here is how to manually map PDF fields when automation is not enough.
Manually map PDF fields: the short version
To manually map PDF fields, work through four stages: choose your parent and child tables, map the parent columns, map the child tables, then review and apply. Validation rules catch structural problems before you generate anything.
When to manually map PDF fields
ExForms offers deterministic mapping, AI-assisted mapping, and this manual flow. Reach for the option to manually map PDF fields when field names do not resemble your headers, when a form pulls from more than one table, or when you simply want full control over every match.
How to manually map PDF fields: the four stages
Stage 1 — Select parent and child tables
Pick exactly one parent table — this is the table that drives how many documents you get, one per row. Keep genuinely related tables checked as child tables, and uncheck anything the form does not use.
Stage 2 — Map parent columns
Match your parent table’s Excel headers to the PDF’s form fields. These are the values that appear once per document.
Stage 3 — Map child tables
Do the same for child table headers. Child data is the repeating part — line items, dependants, transactions.
Stage 4 — Review and apply
Check the full mapping in one view, then apply it. The mapping is saved with the set, so future runs reuse it.
Validation rules worth knowing
Stage 1 enforces a few rules that prevent broken output later:
- Exactly one parent table is required.
- At least one used table is required.
- Every used table must contain an ID column.
- Child tables without an ID are ignored automatically and cannot be selected.
- Header names within a used table must be unique — duplicates are rejected.
If a table is not appearing where you expect, it is almost always a missing ID column or a duplicate header.
Parent and child, briefly
The parent table is one row per document. Child tables hold the many-rows-per-document data linked back by ID. Getting this relationship right up front is what makes a complex form fill correctly.
Common questions
Manually map PDF fields with confidence
Work through the stages once and the mapping is reusable forever. Full details, including every validation rule, are in the Manual Mapping guide.
About the Author: Catalin
