Full name
full_name stores a person's name as components that can be edited and queried separately while
displaying as one value: an optional title, a first_name and a last_name. Use it where a
record names a person. Use text for names of things, and keep existing free-text name attributes
as they are: attribute types are immutable and no automatic splitting is attempted.
Valueโ
{ "title": "Dr. Mag.", "first_name": "Anna", "last_name": "Muster" }
| Member | Rules |
|---|---|
title | Optional. Academic or professional titles exactly as entered, such as Dr., Mag., Prof. or Dr. Mag.. There is no list of allowed titles and no reordering. At most 50 characters. |
first_name | Optional. At most 100 characters. |
last_name | Optional. At most 100 characters. |
Members are trimmed and runs of whitespace collapse to one space. A blank member is dropped, so a
read never returns "" or null members. Single-part names are valid: at least one of
first_name and last_name must be present. A title without a name returns
422 full-name-component-required.
A supplied value replaces the stored value entirely. Sending {"first_name": "Anna", "last_name": "Muster"} removes a stored title, and sending {"title": "Prof.", "last_name": "Muster"} removes the stored first name. Clients that edit one member send the full structure.
Empty valuesโ
A value whose members are all blank, such as {} or {"first_name": " "}, is empty. It clears
the attribute exactly like null: an optional attribute is removed and a required one returns
422 required-field. Reads never return an empty object.
Validation errorsโ
| Error type | Cause |
|---|---|
type-mismatch | The value is not an object, or a member is not a string. The pointer names the member, for example #/data/contact/title. |
unknown-field | A member other than title, first_name or last_name. |
string-too-long | A member exceeds its length limit. |
full-name-component-required | A title was supplied without a first or last name. |
Displayโ
Display templates, automatic display names, compact list cells, the GraphQL display field and
the search index use one policy: title first_name last_name joined by single spaces, skipping
missing parts. Dr. Mag. Anna Muster, Anna Muster, Prof. Muster and Muster are all
rendered without extra spaces or placeholder text. Locale-specific name orders are not offered.
Definitionโ
{
"slug": "contact",
"type": "full_name",
"name": {"en": "Contact", "de": "Kontakt"},
"config": {"is_required": false}
}
| Configuration | Behavior |
|---|---|
is_required | A value with at least a first or last name must be present. |
default | Not available. |
is_unique | Not supported; returns 422 unique-unsupported-type. |
Query capabilitiesโ
| Surface | Capability |
|---|---|
REST filter_operators | contains and is_null (is_null only for optional attributes) |
REST is_sortable | true: orders by last_name, then first_name, case-insensitively |
| GraphQL output | RecordFullName { title: String, first_name: String, last_name: String, display: String! } |
| GraphQL filter | FullNameOperators with _contains and _is_null |
GraphQL order_by | Available, same order as REST |
| Search | The combined display text is indexed; member names are not |
contains matches the combined display text case-insensitively, so "anna must" matches
Dr. Anna Muster. Filters on a single member are not published: a contains operand is matched
against the whole name. Equality, prefix and suffix operators return
422 filter-operator-not-applicable.
Integration surfacesโ
Webhook payloads, MCP record tools, workflow record operations and Vehicle definitions carry the
same object inside data, exactly as REST returns it. Titles travel with the value through every
surface and are never merged into the name members.