Important: This topic is for the Classic Record experience. To view the content for the Next Generation Record experience see Records. For information on Classic experiences, see Archer Classic Experiences.
The Data Import feature enables you to import records into an application, questionnaire, or sub-form from an external data file. Importing data through the Data Import feature rather than entering it manually can save you a lot of time. With good preparation, a data import can be completed quickly and easily.
On this page
File Format for data Imports
The import file must be a flat, delimited-values data file. A flat file contains all data in a single table and does not include any hierarchical structure. The following information applies to a delimited file format:
- Each row is equal to 1 record, and field values are separated in each record by a comma, tab, or other designated character.
- If your file contains multiple values in individual fields, those values are separated with a secondary delimiter, such as a semicolon or pipe (|).
- If your Field Delimiter is a character that appears in individual field values, for example, a comma that separates text strings, the system reads those characters as delimiters. The delimiters separate the field data that comes before and after the commas into 2 separate field values. Do 1 of the following to ensure that this does not occur:
- Use single or double quotes to enclose field values in your data file, for example, "Server, Router." Characters enclosed in quotation marks are not interpreted as delimiters.
- Choose Field and Values Delimiters for your data file that do not occur anywhere in your field values. The pipe (|) and circumflex accent (^) characters are good examples of uncommon characters that work well as delimiters.
Importing Data into Leveled Applications
When importing data into a leveled application, you must import the data separately for each level, starting with the top level. You create separate source files by first exporting data from each level that contains data that you want to import.
For each level you must run an advanced search that includes only the fields for a specific level and a parent-level field. During mapping, you match each data level to the appropriate level fields and the parent level data to the appropriate parent level field. This creates the association between the parent and child levels.
Important: Importing individual columns into specific levels from a single file creates duplicate upper-level records and lower-level records are not associated with their parent records.
Your level-2 import file must contain:
- All the level-2 field values you want to import.
- The unique values for a field in level 1 of the application, such as the Tracking ID field.
Your level-3 import file must contain:
- All the level-3 field values you want to import.
- The unique values for a field in level 2 of the application, such as the Tracking ID field.
