When you export data from an app containing repeatable sections, Fulcrum organizes the information into separate files (CSV) or sheets (Excel). Each repeatable section is treated as its own dataset. This structure ensures data integrity and allows you to re-establish relationships between records in external software.
Core ID Column Definitions
Fulcrum includes specific ID columns to link records across your datasets. The terminology depends on whether you use the Exporter or Downloader.
Record ID: The unique identifier for the specific entry you are viewing.
Parent ID: Found only in repeatable section datasets; this contains the Record ID of the immediate parent.
Root Record ID: Found only in nested repeatable sections; this contains the Record ID of the top-level (original) parent record.
Identification by Tool Type
You can identify how a file was generated by looking for the leading underscore in header names.
Exporter: Uses standard naming (e.g.,
fulcrum_id,fulcrum_parent_id).Downloader: Uses underscores (e.g.,
_record_id,_parent_id). In this tool, the_record_idheader refers to the Root Record, while_child_record_idrefers to the specific entry.
Data Structure Example
If your app uses nested repeatable sections, the hierarchy follows this path: Root Level Parent → Child (Level 1) → Child (Level 2) → Child (Level 3).
Exporter Mapping
A Level 3 child file contains:
fulcrum_parent_id: Links to the Level 2 parent.fulcrum_record_id: Links to the Root Level parent.
Downloader Mapping
A Level 3 child file contains:
_parent_id: Links to the Level 2 parent._record_id: Links to the Root Level parent._child_record_id: The ID for the Level 3 record itself.
Linking Records Externally
To recreate these connections outside of Fulcrum, map the ID columns between your primary and secondary files.
For Immediate Parent Links: Match the
fulcrum_id(Exporter) or_child_record_id(Downloader) in the parent file to theparent_idin the child file.For Root-Level Links: Match the
fulcrum_id(Exporter) or_record_id(Downloader) from the root file to the corresponding root ID column in any child file.
Notes
Always ensure you are using the correct "parent" file when working with deeply nested sections.
The leading underscore is the quickest way to distinguish between Downloader and Exporter datasets.