After dragging an input source onto the canvas, the configuration dialog displays with a Mappings tab. Using this tab, you can review the suggested mappings and manually update a mapping as needed using either Basic or Advanced mode.
- Basic provides you with a smaller set of selections in the list box. Refer to Basic Mapping Columns for a list.
- Advanced allows you to select from a list of all available supported columns when manually mapping, including all the columns in the Basic mode, along with the address lines by number and all the multiple element mapping options such as SecondFullname.
Mappings that are set in the Input task carry into all Processing tasks that are linked to them, as in this example.
NOTE: If you were using a version of Cortex prior to 1.0.7, your mappings created in those older versions will still be maintained on the Process task (Matching, Normalization, Addressing). The Mappings tab will not display on the input task for these workflows, but will display as they did in the older version. All new workflows created in Cortex 1.0.7 and later include the Mappings tab on the Input step.
If a column has been selected to map, it no longer displays as an option in the list box while setting other mappings.
Using Basic Mode
For single input sources, Cortex sets the Basic mode by default.
To use Basic mode:
- Drag an input source onto the canvas and configure it..
- On the Mappings tab, ensure the Basic option is selected.
- Review the suggested mappings, and update as needed.
Using Advanced Mode
If you are mapping multiple input sources using an overlap, join or other method, Advanced is the default setting.
If columns are out of order, or if you need to map multiple elements, such as SecondAddress1, SecondAddress2 and so on, use the Advanced mode to view the full list of all available supported columns when manually mapping. The order of display in the list boxes is:
- All the columns used in Basic mode
- Custom fields
- Multiple elements (SecondCity, ThirdCity)
NOTE: Multiple Other fields have been removed from this list, and only display when they are mapped to a column.
To use Advanced Mode:
- Drag an input source onto the canvas.
- On the Mappings tab, select the Advanced option.
- Review the suggested options, and update as needed.
Resetting Default Mappings
You can click the Reset Mappings button to return the selections in the list boxes in the Mapping column to their suggested default mapping.
Setting Default Mappings
You can add, edit, and remove column header aliases to change how Cortex detects mappings based on header records on the Column Header Alias Editor. You can also view all field mappings Cortex uses from this dialog.
NOTE: Some SAP field mappings have been added to the column heading aliases. Refer to SAP Column Aliases for more information.
To update an alias:
- Click Config in the Menu bar to open the Cortex Properties dialog.
- Click the Column Header Aliases button to set the default mappings for columns.
-
Select the column from the Column Type list box.
-
Click the Add button.
-
Enter the column alias in the blank row.
NOTE: The alias may contain “ _ - + and any alphanumeric character. -
Select an option in the Region list box.
NOTE: This sets the region in which this mapping is applied, Options are:
- Global
- UK
- USA
- Other
- Click Save.
Whenever a column with this alias is included in an input task, it will be mapped to this new value.
NOTE: You can reset the selected Column Type to its default values by clicking the Use Default Aliases button.
Changes to column header aliases are stored by default on your local drive in the file C:\Cortex\bin\ColumnHeaderAlias.xml\. You can reuse this file in another installation of Cortex to reuse the aliases across projects.
Unmapping a Column
If a column should not be mapped, select Other from the corresponding Mapping list box. This option always displays near the top of the list in either Basic or Advanced mode.
The mapping name Other is updated to Other2, Other3 and so on when multiple columns are mapped to this value. The fields Other1-300 only display in the list box if they have been mapped to a value. Unmapped Other fields do not display, making the list less cluttered.
Basic Mapping Columns
US Column |
UK or Other Column (if different) |
Other |
|
UniqueRef |
|
UniqueRefMatch |
|
Fullname |
|
Prefix |
|
FirstName |
|
MiddleNames |
|
Initials |
|
LastName |
|
Qualification |
|
Suffix |
|
Organization NOTE: The alias is Company when used in mappings. |
|
Department |
|
JobTitle |
|
AddressLine |
|
City |
Town |
State |
County for UK, Region for Other |
Zip |
Postcode |
Zip5 |
PostOut |
Plus4 |
PostIn |
DeliveryPoint |
|
Country |
|
Telephone |
|
Mobile |
|
Fax |
|
|
|
DateOfBirth |
|
Website |
|
CustomField1 |
|
NOTE: The following fields are hidden unless the previous number has been used. |
|
CustomField2 |
|
CustomField3 |
|
CustomField4 |
|
CustomField5 |
|
CustomField6 |
|
CustomField7 |
|
CustomField8 |
|
CustomField9 |
SAP Column Aliases
SAP Field |
Mapped to: |
NAME1 |
Fullname |
STRAS |
Address1 |
PSTLZ |
Postcode |
ORT01 |
Town |
REGIO |
Region |
TELF1 |
Telephone |
TELFX |
Fax |
CITY1 |
Address2 |
CITY2 |
Address3 |
STREET |
-Address1 |
HOUSE_NUM1 |
- |
HOUSE_NUM2 |
- |
STR_SUPPL1 |
- |
STR_SUPPL2 |
- |
STR_SUPPL3 |
- |
ADR03 |
Address2 |
ADR04 |
Address3 |