2022.1

l Each Record: These properties are evaluated and set at the beginning of each
source record. Once they have been set, these properties can be modified via an
Action step (see "Action step" on page288), but they are always reset at the
beginning of each source record.
l Type: The data type of the property. For more information see "Data types" on page310.
l Debug Value: The initial value of the property. This is a JavaScript expression. See
"DataMapper Scripts API" on page408.
Note
Since Entire data properties are evaluated before anything else, such as
Preprocessors, Delimiters and Boundaries in the Settings pane (see "Data
source settings" on page249), these properties cannot read information from the
data sample or from any records.
Preprocessor
The Preprocessor subsection defines what preprocessor tasks are performed on the data file
before it is handed over to the data mapping workflow. Preprocessor tasks can modify the data
file in many ways, and each task runs in turn, using the result of the previous one as an input.
l Name: The name to identify the Preprocessor task. Click this field to rename the
Preprocessor task.
l Type: The type of Preprocessor task. Currently there is only one type available: script.
The buttons to the right can be used to add, remove and reorder the tasks and to apply them to
the current data file.
Note
The Apply button has an effect at design time only. It is ignored at runtime. When a data
mapping configuration is executed on the server, all preprocessors are executed in
original order.
Page 368