2022.1

Note
l Imported Data Model fields always overwrite existing field properties when the field
name is the same (although they will still be part of the same Extract step). Non-
existent fields are created automatically with the appropriate field settings. The
import is case-insensitive.
l All imported data model fields are marked as required in the Data Model (indicated
with an asterisk (*) next to their names). This is to prevent them from being removed,
as the DataMapper immediately discards non-required fields that are not referenced
by any Extract step.
Editing the Data Model
The Data Model is generally constructed by extracting data; see "Extracting data" on page256.
Empty fields and data tables can be added via the contextual menu; see "Adding empty fields
via the Data Model pane" on page298.
Editing fields
You can modify the fields in the Data Model via the contextual menu that opens when you right-
click on something in the Data Model pane. For an explanation of the options in this menu, see
"Data Model contextual menu" on page333.
As long as a field or data table, added via the Data Model pane, remains empty, it can be
edited (renamed, deleted etc.) via the contextual menu.
Fields in a Data Model that are actually used in the extraction workflow cannot be edited via the
contextual menu of the Data Model pane. They are related to a step in the extraction workflow
and are edited via the Step properties pane instead (see "Editing fields" on page299).
Ordering and grouping fields 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. All grouping and ordering information is saved in the data
mapping configuration, so that when you reopen it, the Data Model will look the same.
Note that these changes have no impact on the order in which data are extracted, or on the final
records in the OL Connect database. They only help you organize the Data Model visually.
This also means group names are not used in scripts; fields and detail tables are accessed
Page 293