Custom object instances
Create individual records of a custom object you've defined, and manage them like any other content
Once you've defined a custom object, the records you create from it are called instances. If you've defined a "Sponsor" object, each sponsor you add is a Sponsor instance. The structure is fixed by the object definition; the content of each instance is what you fill in.
Creating an instance
Open the custom object's admin area. The list shows every instance you've created. Add a new one and fill in the fields the object defines.
Instances behave like other content in Basker:
- They have a title — usually drawn from the most identifying field, like name or label.
- They support drafts and publishing — see Drafts and preview.
- They support versioning — see Versioning and history.
- Their fields can be translated — see Languages and translation.
Referencing an instance from other content
Custom object instances can be referenced from any relationship field that points at the object. Add a "Sponsors" relationship attribute on events, and each event editor gains a picker for choosing sponsor instances.
The same instance can be referenced from as many records as you need. Updating the instance updates everywhere it's used.
Listing instances on your site
Whether and how custom object instances appear on the live site depends on your theme. If the theme exposes blocks that render the object — for example, a "Sponsor wall" block — those blocks will pick up the instances you've created. If the theme doesn't, instances stay internal and only appear via fields they're referenced from.
Smart collections work with custom objects too: you can build a smart collection of instances that match certain conditions, and the collection has its own page on the site.