This section contains information about:

A mapping file determines which pieces of data to import into the fields on the target form (mapping) during the import process. You can map all fields in a data file to all fields in a form, or you can map fields individually.

Data Import matches data fields to form fields as follows:

• AR Export or AR XML — Field IDs are matched first, and then field names are matched for fields without matching IDs.
• CSV or ASCII — Only field names are matched.

You can define fallback mappings, which are default mappings that direct the Data Import response if a data mapping problem occurs during an import. Fallback mappings are used when the data value is invalid for the destination form field type. For example, if a problem occurs while a value is mapped, the fallback mapping for the field is used if one is defined. If no fallback mapping exists, an error is generated. If a fallback mapping fails, errors are generated on the original failed mapping, not the fallback mapping.

When only the AR System server can detect the error (such as when the data is not an acceptable value), the fallback mapping is not used. For example, the data value is outside the range set for the form field, or a required field has a NULL value.