Multiple-Value Additional Field Data Set Table

There are two different data sets for populating multiple-value additional fields:

• Multiple-Value Field populates regular single-value additional fields
• Multiple-Value, Multiple Column data set populates fields that use the Variable Field Additional Field Extension.

For details about configuring additional field data sets, see Overview of the Additional Field Data Sets.

Multiple-Value Additional Fields Data Set

Table Column	Description
SYS_ID	System ID for the contact to update with the additional field value in the row. This column only applies when mapping by Data Source System ID.
LISTING_ID	InterAction Contact ID of the contact to update with the additional field value in this row. This column only applies when mapping by InterAction Contact ID (ListingID). The contact ID is called Listing ID in previous versions and in the InterAction database.
LISTING_SRC_ID	InterAction Contact Source ID of the contact to update with the additional field value in this row. This column only applies when mapping by InterAction Contact ID (ListingID). The Contact Source ID identifies the database on which the contact was created. Combined with the Contact ID, it uniquely identifies the contact. The contact Source ID is called Listing Source ID in previous versions and in the InterAction database.
MV_SYS_ID	Multiple-value system ID. This ID uniquely identifies each value in the multiple value field. If your external system includes unique identifiers for each value, harvest those values into this column. If the system does not provide these identifiers, you can use the Replace Data option. You still must harvest unique values into this field. Note: The ID values you use in the MV_SYS_ID column must be positive numbers; do not use negative numbers.
RELATIONSHIP_FIELD	Secondary field for a multiple-value field. In InterAction, this field is used to collect any additional information about the field value, and it can be renamed. For example, the Recommended By multi-value field might call the secondary field Comments.
[FIELD_TO_POPULATE]	The table contains a a column for each InterAction additional field to populate, renamed to be a valid SQL column name. For example, the field Billings 2000 becomes BILLINGS_2000.
[MAPPING_FIELD]	This column displays if you choose to map contacts using an additional field value. The value in this column is used to find the contacts to update with the additional field values harvested in the previous columns. The column is renamed to a valid SQL column name - for example, Client Code becomes CLIENT_CODE.

Multiple-Value, Multi-Column Additional Fields Data Set

Table Column	Description
SYS_ID	System ID for the contact to update with the additional field values in the row. This column is only included when mapping by Data Source System ID.
LISTING_ID	InterAction Contact ID of the contact to update with the additional field values in this row. This column only applies when mapping by InterAction Contact ID (ListingID). The contact ID is called Listing ID in previous versions and in the InterAction database.
LISTING_SRC_ID	InterAction Contact Source ID of the contact to update with the additional field values in this row. This column only applies when mapping by InterAction Contact ID (ListingID). The Contact Source ID identifies the database on which the contact was created. Combined with the Contact ID, it uniquely identifies the contact. The contact Source ID is called Listing Source ID in previous versions and in the InterAction database.
MV_SYS_ID	Multiple-value system ID. This ID uniquely identifies each value in the multiple value field. If your external system includes unique identifiers for each value, harvest those values into this column. If the system does not provide these identifiers, you can use the Replace Data option. You still must harvest unique values into this field.
[COLUMNS_TO_POPULATE]	The table contains a column for each InterAction column configured for the variable field additional field extension, renamed to be a valid SQL column name.
[MAPPING_FIELD]	This column displays if you choose to map contacts using an additional field value. The value in this column is used to find the contacts to update with the additional field values harvested in the previous columns. The column is renamed to a valid SQL column name - for example, Client Code becomes CLIENT_CODE.