2019.1

Table Of Contents
Comments: The text entered here will be displayed in the tooltip that appears when hovering
over the step in the Steps pane.
Extraction Definition
l
Data Table: Defines where the data will be placed in the extracted record. The root table
is record, any other table inside the record is a detail table. For more information see
"Extracting transactional data" on page244.
l
Append values to current record: When the Extract step is inside a loop, check this to
ensure that the extraction will be done in the same detail table as any previous
extractions within the same loop. This ensures that, if multiple extracts are present, only
one detail table is created.
Field Definition
The following field definition settings are identical for all fields.
l
Field List: The Field List displays each of the single fields that belong to the selected
step in a drop-down. Fields can be re-ordered and re-named within the Order and rename
fields dialog (see "Order and rename fields dialog" on page350). Select one of the fields
to make further settings for that field.
l
Add Unique ID to extraction field: Check to add a unique numerical set of characters to
the end of the extracted value. This ensures no two values are identical in this field in the
record set.
l
Mode: Determines the origin of the data. Fields always belong to an Extract step, but they
don't necessarily contain extracted data. See "Fields" on page275 for more information.
l
Location: The contents of the data selection determine the value of the extracted
field. The settings for location-based fields are listed separately, per file type:
l "Settings for location-based fields in a Text file" on the facing page
l "Settings for location-based fields in a PDF File" on page347
l "Settings for location-based fields in CSV and Database files" on page348
l "Settings for location-based fields in an XML File" on page348
l
JavaScript : The result of the JavaScript Expression written below the drop-down
will be the value of the extracted field. If the expression contains multiple lines, the
last value attribution (variable = "value";) will be the value. See DataMapper API.
Page 345