Response body for the custom-properties bag on a field definition. The bag is an opaque application-defined string → string map persisted on the field definition itself (scoped to the definition, not to a user). Use it to attach integration metadata or application-specific configuration that belongs with the field — for example to encode list-field display preferences such as sort order, or to record an external system's identifier for the field. Keys are application-defined; the API does not validate semantic meaning. Recommend namespaced keys to avoid collisions, e.g. com.acme.invoice.region or myapp.ingest.batch_id. The response may include entries written by other applications or by system-managed tooling; callers should leave unrecognized keys untouched on subsequent updates.
Response body for the custom-properties bag on a field definition. The bag is an opaque application-defined string → string map persisted on the field definition itself (scoped to the definition, not to a user). Use it to attach integration metadata or application-specific configuration that belongs with the field — for example to encode list-field display preferences such as sort order, or to record an external system's identifier for the field. Keys are application-defined; the API does not validate semantic meaning. Recommend namespaced keys to avoid collisions, e.g. com.acme.invoice.region or myapp.ingest.batch_id. The response may include entries written by other applications or by system-managed tooling; callers should leave unrecognized keys untouched on subsequent updates.