Setup & integrations

Import a dictionary

Bulk-load the dictionary from a CSV. The fastest way to stand up a new Org's dictionary or refresh a stale one.

Customer-app route: /settings/data-dictionary/import
Who uses this: Every authenticated team member.

What it is

The CSV importer. Drop a CSV with a row per field; the importer tells you how many rows created, how many updated, and any errors per row.

CSV columns

field_name — exact Slate column.
label — human-friendly name.
type — one of text, number, date, boolean, enum.
description — semantic explanation.
allowed_values — pipe-delimited for enum types, blank otherwise.

Common workflows

Initial bulk load

Export your Slate field schema as CSV.
Format columns to match the spec above.
Upload here.
Confirm the imported / created / updated counts match expectations.

Refresh after Slate schema change

Re-export the field schema.
Re-import. Existing entries with the same field_name update in place.

Common gotchas

Import shows row errors

The error count points at malformed rows — usually missing the type column or an enum row missing allowed_values.

Import succeeded but Celia didn't pick it up

Wait for the next Flow run. Existing analyses use the dictionary as it was when they ran.