Skip to main content
Custom objects let you model data ConveYour has no built-in type for — a vehicle, a certification, a job site — where the object defines the schema and records are the rows stored against it. This exists so your account can hold the things your process depends on without forcing them into contact fields.

​
Custom Objects

A custom object is the schema blueprint for a record type you define — its fields, its relations to contacts and to other custom objects, and what a contact may do with its records in the learner portal. Fields can be Text, TextArea, Number, Checkbox, Date, DateTime, Select, Liquid, Image, List, ListSelect or Relation. It exists so you can model data ConveYour has no built-in type for: the object is the class definition, and records are the instances.

​
Custom Object Records

A record is a single row of a custom object, validated against that object’s own schema layered over the shared defaults — which is why the field set varies from one organization and object to the next. They exist to hold the actual data the object describes: the object is the shape, records are the rows. Records can be upserted by external_id, so an outside system can keep them in sync without tracking ConveYour’s own IDs, and changing one can sync values back onto related contact fields.