Advanced Mapping: Importing Data into Repeaters
A repeater allows a section of your form to be duplicated, which is perfect for lists of information like emergency contacts. This guide explains how to map data from your import file to the fields inside a repeater.
Before you begin, ensure your source file is formatted correctly for a repeater import.
- For untransformed CSV files, data must be tab-separated within a single cell.
- For transformed data, your final XML must use <instance> nodes.
For a full explanation of these requirements, please see the file preparation articles in the
Getting Started Section.
How Repeater Mapping is Different
The process for mapping a field inside a repeater is nearly identical to mapping a standard field, with one key difference: you must select a field that is located inside a repeater section.
Once you select a field inside the repeater and map a source column to it (e.g., {ContactNames}), the system automatically handles the rest. It will detect the separated data (from tabs or <instance> nodes) and create as many repeater instances as needed.
You do not use indexed expressions like {Column[0]} for this process.
For the general, step-by-step process of using the Import Panel (selecting the Source, Alias, and Expression), please refer to our guide on basic mapping.
Important Note on Unmapped Fields
Warning: When you import data into a repeater, any field inside that repeater that you do not map will have its existing data cleared. The import process assumes your source file is the complete source of truth for the repeater, so be sure to map every field within the repeater that you want to retain data.
Next Steps
You've now learned how to map data into dynamic, repeatable sections. Depending on your import needs, you can either continue to the next advanced mapping topic or move on to learn about data transformations.
Path 1: Continue with Advanced Mapping
If your import requires mapping multiple source rows into different static sections of your form (e.g., Guardian 1, Guardian 2), the next article is for you.
If you don't need to use indexed expressions and are ready to learn how to clean, restructure, or modify your data before it's imported, you can proceed to the next major section.
Related Articles
Advanced Mapping: Using Indexed Expressions
While repeaters handle lists of data that can grow or shrink, sometimes you have a fixed number of related entries to import into separate, static sections of a form. A common example is importing contact information into predefined "Guardian 1" and ...
Introduction to Field Mapping
Once you have an Import Configuration set up, the next critical step is field mapping. This is the process of telling the system exactly which column from your source file should populate which field on your form. This connection is made directly ...
Overview of the Import Process
The Import Module is a powerful tool for bringing external data directly into your forms. It streamlines workflows, reduces manual entry, and enhances data accuracy by using structured files like CSV, TSV, XML, or JSON to automatically populate or ...
Introduction to Import Data Transformation
Sometimes, the data in your source file isn't in the exact structure or format that your forms require. Data Transformation is an optional but powerful step in the import process that allows you to clean, restructure, and manipulate your source data ...
Preparing a CSV or TSV File for Import
A correctly formatted CSV (Comma-Separated Values) or TSV (Tab-Separated Values) file is essential for a successful import. While these are standard formats, your file must adhere to specific rules to ensure data is processed accurately. Basic File ...