Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Open the mapper with an external PDF viewer/editor, such as Adobe Reader (version 11 or higher) or Mac Preview.
Note |
---|
PDF.js, a PDF Viewer available for the Firefox browser, may not render the PDF properly. If you are using this as your viewer, and the PDf does not look as expected, download the PDF and view it in Adobe or Mac Preview. |
Previous mapping selections should be retained. There There are some forms where Adobe reader may loose the previous mappings. If this is the case, all fields will have to be manually mapped again. Here is an example of the downloaded mapper for the W-4 PDF. Notice the Acroform fields are re-written with editable combo box controls. The combo boxes are pre-populated with the names of relevant e-form fields from the flow for the purposes of field mapping.
...
Info |
---|
Adobe Reader supports the linkage of fields. This means that Acroform fields can share the same values even if the fields have different names. For example: Let's say you have an Acroform pdf consisting of 8 pages. Writable fields for Name, Address, City, State and Zip Code are located on the first, third, fifth and eighth pages. If you are using Adobe Reader to map your PDF, then you can map the Name and Address fields in the mapper on the first page and the Name and Address fields on pages three, five and eight will automatically become mapped. Adobe enforces the link between these fields even though the field names are different. (the Name field on the first page is named topmostSubform[0].Page1[0].f1... while the Name field on the third page is topmostSubform[0].Page3[0].f1...). If you are using Adobe Reader, you cannot map the fields on pages three, five and eight separately. If you are using a mapper that does not support field linkage, such as Mac Preview and or PDFEscape, you will have to map the Name and Address fields on each page. |
...