2021.2

Note
About field names:
l Fields cannot have the same name, unless they are located on a different level in
the record (e.g. root level, detail table).
l It is recommended that you do not use spaces in field names.
When a data field is dragged into a template, the data field name is used in the
selector of the script that is created, but any spaces will be removed.
Also, data fields may be used as Metadata in a Workflow process, and spaces are
not permitted in Metadata field names.
Note
The order of fields in an extraction step may be different from their order in the Data
Model. To make the Data Model clearer and more manageable, you can change the
order of the fields in it and create groups of fields. See also: "Ordering and grouping fields
in the Data Model" on page269.
Setting the data type
Fields store extracted data as a String by default. The data type of a field can be changed via
the properties of the Extract step that the field belongs to.
1. Select the Extract step that contains the field. You can do this by clicking on the field in
the Data Model, or on the step in the Steps pane that contains the field.
2. On the Step properties pane, under Field Definition, set the Type to the desired data type.
See "Data types" on page286 for a list of available types.
Changing the type does not only set the data type inside the record. In the case of dates,
numbers and currencies, it also means that the DataMapper will expect the data in the data
source to be formatted in a certain way. If the actual data doesn't match the format that the
DataMapper expects, it cannot interpret the date, number or currency as such. If for example a
date in the data source is formatted as "yyyy-mm-dd" but the default format adds the time, the
date cannot be read and the DataMapper will stop with an error.
Page 276