The Data Mappings subtable on the Mappings page of the Data Import Definitions application is used to map either a user defined constant value or fields from an imported file to fields in an platform table. The Destination Field in the subtable is where you select the field you want to map values into. Learn more in Data import mapping configuration.
Dependent table lookups must be used when you configure the Destination Field with multiple values, and one of those values is itself a table lookup. For example, you may want to map values into a GL Account. Companies with multiple organizations may use different account numbers for their different Charts. To ensure you have the correct GL account when you import, you may make the GL Account number field dependent on an additional lookup value such as the Chart name.
Example Configuration
In the Company Structure application, you may need to map your imported values to the Name field. In some instances, the Name field alone is not enough to identify the correct record, so you would need to add a Controlling Lookup, such as the Org Unit Type field, that further identifies the correct placement for the imported value.
To achieve this, you would need to create the following records in the Data Mappings subtable:
- A Controlling Lookup that is a lookup for the Org Unit Type.
- A Dependent lookup with a Source Field of Name, and a Destination Field of Org Unit Type.
- A Table Lookup on the Controlling Lookup, in this case the Org Unit Type.
- A Table Lookup on the Dependent lookup, in this case the Name field.
To configure, in the Data Mappings subtable, you would fill in the following fields for your Controlling Lookup:
- In the Destination Field, you must enter a value that is in the records you are importing, and also in the platform table you are importing the records into. Unlike most lookups, this does not need to be a field in the Destination Table, but it still needs to be a valid Table Lookup data item that has a Related Table defined.
- In the Mapping Options field, you can specify the -support=value syntax option where value is the name of the controlling lookup to be used by the dependent lookup. For example, -support=Name.
| Source Type | Source Field | Destination Field | Type | Mapping Type | Mapping Sub Type | Mapping Options |
|---|---|---|---|---|---|---|
| Header | Org Unit Type | Org Unit Type | Table Lookup | Controlling Lookup | Table Lookup By Value | -support=Name |
Then, you would fill in the following fields for your Dependent Lookup:
- In the Source Field, enter the same source field from the controlling lookup unless there is a mapping option of -support specified. If there is, you must reference the value from the mapping option. For example, if the mapping option is -support=Name, you would specify name in the source field of your dependent lookup.
- In the Destination Field, enter the value you want your source field to be dependent on.
- In the Mapping Sub Type field, select
Table Lookup By ValueorTable Lookup by Multiple Values.
| Source Type | Source Field | Destination Field | Type | Mapping Type | Mapping Sub Type | Mapping Options |
|---|---|---|---|---|---|---|
| Dependent | Name | Org Unit Type | Table Lookup | Table Lookup | Table Lookup By Value |
Then, you would create individual records for the Controlling and Dependent Lookups. To configure, you would fill in the following fields:
- The table lookup on the dependent lookup would use the same source field value as defined in the dependent lookup.
- The table lookup on the controlling lookup would use the same source field value as the controlling lookup.
- In the Mapping Sub Type field, select
Table Lookup By ValueorTable Lookup by Multiple Values.
| Source Type | Source Field | Destination Field | Type | Mapping Type | Mapping Sub Type | Mapping Options |
|---|---|---|---|---|---|---|
| Header | Name | Org Unit Type | Table Lookup | Table Lookup | Table Lookup By Value | |
| Header | Name | Name | Table Lookup | Table Lookup | Table Lookup By Value |