The Terminus ID field surfaces a record’s built-in unique identifier, in the format
trm0 followed by lowercase alphanumeric characters. It is generated by the system, so submitters never type it.When to use it
Reach for Terminus ID when you need a stable handle on a record:- A reliable identifier that outlives any single submission and never changes.
- The code field of an automated picklist level, so other taxonomies reference each record by a code that stays put even when its display name changes.
- A dependable value to feed into a Concatenation field.
How it works
Every record carries a Terminus ID, assigned the first time it is created and unchanging from then on. The identifier is unique across your account. A Terminus ID field surfaces that identifier as a field value, so it can show in the grid, feed into a Concatenation field, or serve as the option code of an automated picklist. The field is not a second, independent identifier: it mirrors the record’s own Terminus ID.Settings reference
Terminus ID has no configurable settings. The format and value are system-generated and cannot be changed.Example
A Clients taxonomy has a Terminus ID field named Client ID so other taxonomies can reference each client by a stable code. It has no type-specific settings; only the shared ones such as Name, Description, and Field handle. A client record resolves to something liketrm0kf8m2a1q. An automated picklist sourced from Clients can then use Client ID as a level (the field that supplies each option’s code), with the client name as its Label field. A dropdown on a Campaigns taxonomy that uses this picklist stores the client’s Terminus ID, a reference that survives even if the client’s name later changes.
Gotchas
- There are no settings. You cannot change the format, length, or add a prefix or suffix.
- It is fixed and unique. The value is assigned once when the record is created and is unique across your account, which is what makes it safe to use as a reference.
- One per taxonomy. A taxonomy can use at most one Terminus ID field. Publishing a model where a taxonomy has two is rejected with “taxonomy can have only one terminus_id field”.
- It mirrors the record’s identifier. It is the record’s own Terminus ID made visible, not a separate ID.
- It is read-only. The value is generated for you and there is nothing to set or edit in the submission form.
Related
- Fields
- Automated picklist: commonly uses a Terminus ID field as a level.
- Auto Number field: a sequential alternative when you want readable numbers.
- Computed fields