Import CSV data

CSV Import requires the Import module and a supported local Objects or Regions Collection. Import changes shared records, so back up the destination before replacing existing data.

Download the sample office metadata CSV to try a three-record metadata import. It contains no Location column; add positions separately or retain existing positions when mapping an update. Its numeric category values need matching field choices.

Analyze the file

1. Open Database → Collections and choose the destination.
2. Open Import.
3. Choose the CSV source and select the file.
4. Click Check CSV.
5. Review the detected columns, types, available values, and record count.

Use a header row with stable column names. A file that parses is not automatically mapped correctly: check IDs, dates, coordinates, and empty values explicitly.

Choose identity

Decide whether a CSV column identifies existing records. Map the source ID to the destination key when updating records. For Regions, use the SVG’s exact IDs, for example US-CA rather than California.

No ID means append without a source key where the destination supports generated IDs. Re-importing an append-only file can create duplicates. Do not select No ID merely to bypass an ID mismatch.

Map fields

The mapping table connects CSV columns to Collection fields. Skip columns you do not want. If the import offers to add missing fields, review their types before approving a schema change.

For markers, check the supported Location mapping and geocoding options. Addresses can require Google services; valid coordinates avoid address ambiguity. Preview several records instead of trusting only the first row.

Run and verify

Start the import after reviewing the plan. Replacement and key-conversion choices have separate consequences; read their confirmation before continuing. Keep the progress/log view available and investigate failed rows.

After completion, open Data and inspect representative records. Then open the App, verify its Page Query binding, and test its filters and markers.

Importing records does not require republishing an unchanged App configuration. Changes to the App’s filters, templates, or bindings still belong to its draft and require Publish.