Collections & Fields

Create the collections your work needs and shape them with typed fields.

• GuideWorking with collections and fieldsSonta does not hand you a fixed set of objects — you create the collections your work needs and shape each one with typed fields. This guide walks that: what a collection is, how to create one, how fields carry and connect your data, and when to let a blueprint do the setup for you.
• ArticleCreate a collectionCreate a collection by naming it for what one entry represents, then adding the fields that describe it. You can create it with its fields in one pass or create it bare and add fields as you go. Housekeeping fields — name, identifier, publication state — are added automatically.
• ArticleAdd or change a fieldAdd a field by naming it and choosing its type, then set whether it is required, unique, or searchable. Most settings can be changed later — the type cannot. To retire a field, archive it rather than deleting, and clear any rules that depend on it first.
• ArticleCreate an entryTo create an entry, open the collection, add a new entry, give it a name, and fill in its required fields. It saves as a draft unless the collection defaults to published, and it goes through the same checks whether a person, an agent, an import, or your website creates it.
• ArticleBuild a pipelineTo build a pipeline, open the collection's pipeline, add its stages in order, give each a category (open, closed, or archived), and mark which closed stages are won and lost. Stages live only inside a pipeline, and every collection with stages already has a default one to start from.
• ArticleImport entries from CSVTo import entries from a CSV, upload the file to the collection, map each column to a field or ignore it, choose what happens to rows that match existing entries, and run a dry run before the real import. To update entries rather than create them, export first, edit the file, and import it back with the record id column.