Classifiers

Classifiers are shared values used to describe records consistently. They are useful for categories, types, regions, priorities, industries, reasons, or other controlled choices that users should not type differently each time.

Use a classifier when the value is mainly a label for filtering, reporting, or consistent entry. Use a full record type when the object needs its own fields, relationships, history, access, or lifecycle.

In the product, a classifier is a kind of catalog: a reusable taxonomy whose nodes are administered from the catalog runtime. Simple per-field choice lists are different — those are Select field options configured on the entity’s schema (see Fields and schema). Reach for a classifier when several record types must share one taxonomy.

Classifier fields on records

A Classifier field binds one record field to one Classifier Catalog. Users pick one category from that Catalog, including a non-leaf category when the model requires it. Lists, cards, and details show the category’s current breadcrumb, so renaming or moving a category updates what users see without rewriting every record.

Selecting or changing a category requires read access to the bound Catalog in addition to the ordinary record and field permissions. Losing Catalog read access does not erase an already stored value or prevent unrelated record updates when that value stays unchanged.

Data Explorer filters support exact category, set, null, and branch matching. Is in category branch includes the selected category and all descendants. Is not in category branch excludes that branch and does not include records whose Classifier field is empty. Use the explicit null operators when empty records are required.

Branch filters require read or management access to the bound Catalog. Renaming or reordering a category does not change saved branch filters; moving a category updates their result immediately. If Catalog read access is lost, a saved view keeps the condition but cannot apply it until the condition is removed or access is restored.

Classifier catalog browser

Administrators can place a specific Classifier in a user menu. Its runtime page combines the category tree with one paged list of classified records from every record type that uses that Classifier. The logical root shows all classified records. A selected category shows exact assignments by default and offers an Entire branch scope that includes descendants.

Catalog readers may browse the tree and content, but Catalog access does not grant access to the records themselves. Unreadable records appear only as restricted entries. Users with ordinary record and field update access can add records through the shared picker or remove one concrete field assignment. These changes use the normal record update pipeline and appear in the record’s audit history.

Audit history stores the full category breadcrumb captured when the field changed. Renaming or moving a category updates current record displays but does not rewrite older audit entries.

Validation Rules and Statements also support exact, set, and null comparisons. Use Insert category in either editor to choose a category and insert a portable CATEGORY('catalog-key', 'path-key', ...) value. Rules may compare two Classifier fields only when both use the same Classifier Catalog. Branch matching is a Data Explorer query capability, not a Validation Rule or Statement operator.

Creating or changing a Classifier expression requires Catalog read or management access. Existing Rules and Statements continue to run if the author later loses Catalog access; their other metadata can still be updated while the expression stays unchanged. A category used by a Rule or Statement cannot be deleted or moved with its subtree until that dependency is removed.

JSON data transfer represents a Classifier value as stable category PathKeys relative to its Catalog. CSV export writes the same path as a JSON array cell.