Read target field requirements
Interpret required fields, collections, references and capabilities in the DevRev object catalog.
Field contract and verification
The field tables give type, whether a field is required and reference targets. Required target fields must be mapped or have a supported creation fallback. collection means an array of the listed type. Reference labels such as #record:article and #category:user identify compatible targets, not literal values to send as object IDs.
Test actual required values, enums, empty collections and unresolved references. Verify subtypes and custom fields when supported. For reverse-enabled objects, confirm the external write receives the denormalized values your API accepts. For permissions and teams, test enforcement and relationships in addition to field presence.
Related contracts: transformation methods, permissions, teams, rich text, reverse sync.
Related: supported types, mapping rules.
Last updated on