The Field Mappings area is where the individual data points in the map are specified. If you want to customize the data you are importing, you will need to make changes to the field mappings. Each row in the field mappings represents a single field in the destination table―or API view―you are importing into. The various components of the map are described below:
Specifies if this field should be treated as a key field for the purpose of update and append maps. (Note: This feature is not currently implemented.)
Name of the field on the destination table in the database.
The type of data for the field.
Indicates if this field is required in the database schema. Sometimes the default value in these fields is sufficient to meet the database requirements, while other times the default value is not sufficient.
These options indicate what value should be used for this field:
The default value according to the database schema is used.
The column specified in the Column # field is to be used.
An empty string is to be used for this field.
The value from the alt. value is to be used.
Uses a "NULL" value.
The column # specified is to be used from the CSV file.
If the value read from Column # results in a "NULL" value, then you can provide additional processing using one of the following criteria:
Use the "NULL" value.
Use the default value according to the database schema.
Use an empty string.
Use the value specified in alt. value.
Use the value specified in alt. column #.
The column # specified is to be used from the CSV file if the first column was "NULL" and the If Col. Null action was Use Alt. Column.
If the value read from the Alt. Column # results in a "NULL" value, then you can provide additional processing using one of the following criteria:
Use the "NULL" value.
Use the default value according to the database schema.
Use an empty string.
Use the value specified in alt. value.
This is any text you want to be passed to the field if the option
is specified.