A field is one detail you keep on every record of an object. Open Settings, then Data model, choose an object and add fields under Fields and relations. You can add fields to your own objects and to contacts, companies, deals and tasks.
Field types
| Type | What it keeps |
|---|---|
| Text, Long text, Rich text | A line of text, a longer text, or formatted text |
| Number | A whole number or a decimal, with the number of decimals you choose |
| Currency | An amount with its currency code |
| Yes or no | A switch |
| Date, Date and time | A day, or a day with a time |
| Select, Multi-select | One choice, or several, from a list you define. Each choice can have a colour |
| Rating | 1 to 5 stars |
| Files | One file or several, such as a signed contract or a logo |
| Emails, Phones, Links | A main value plus any number of extra ones |
| Web address | One link |
| Full name | First and last name |
| Address | Street, city, postcode, state and country |
| Member | One person from your workspace |
| Unique ID, JSON, List | An identifier, structured data, or a list of values |
Every value is checked against its type wherever it is saved: on the record page, in a table, in an import, through the API and by an agent. A value that does not fit is refused with a message that names the field.
The type cannot be changed after you add a field, because the values already saved depend on it. To use another type, archive the field and add a new one.
Files
A Files field keeps uploaded files on a record. Choose Most files (1 keeps a single file, up to 10), the Largest file (up to 10 MB) and which kinds of file are accepted: images, PDFs, documents, spreadsheets, audio, video and archives. Leave the kinds empty to accept all of them. They are the same kinds the form builder offers.
On a record, drop files on the field or choose them; each shows its upload progress, can be removed and can be downloaded. A file is checked for malware before it is kept, and the type is read from the file itself, not from its name. Download links expire after 15 minutes. Taking a file off a record, deleting the field for good or deleting the object removes the file from storage in the background. Workspaces on a plan without file storage cannot upload files.
Files are not part of an import, because a CSV cannot carry them: a Files field is not offered as a column target, so add the files on the records afterwards. An export lists the file names.
Required and unique
- Required - a record cannot be saved without a value.
- Unique - no two records may hold the same value. This works for text, number, emails, web address and unique ID fields. If two records already share a value, the field cannot be made unique until you fix them.
A record that is deleted keeps its unique values until it is deleted permanently. While it sits in Deleted records, nobody can save another record with the same value: the error names the deleted record and tells you to restore it, or delete it permanently to use the value again. Restoring a record therefore never clashes. Importing a row that matches a deleted record by a unique field restores that record instead of making a second one.
Choices for select fields
List the choices and give each one a colour if you like. You can rename a choice or change its colour at any time. A choice you take off the list is no longer offered, and records that already hold it keep it.
Archive a field
Archive hides a field from tables, record pages and new entries. The values are kept. Archived fields are listed under Archived, and Restore brings one back with all its values. A field can only be deleted once archived, and deleting it removes its values from every record in the background.
Built-in fields of contacts, companies, deals and tasks
These objects come with fields of their own. They are marked Built in and cannot be renamed or removed, but most can be filtered, sorted, grouped and edited like any other field:
| Object | Built-in fields |
|---|---|
| Contact | Name, email, phone, company, user ID, owner, lifecycle stage, marketing consent, source, last seen |
| Company | Name, domain, size, industry |
| Deal | Title, amount, expected close, pipeline, stage, status, lost reason, owner, contact, company |
| Task | Title, description, due, status, assignee, contact, company, deal |
- Name and company of a contact are read from the details the contact carries (a name, or a first and last name). Filtering by contains looks in all of them.
- Email and phone are kept encrypted, so they match as a whole: is, is not, is any of, is empty. Case, a "+tag" and the way a number is written do not matter. Searching for part of an address or number is not possible, on purpose.
- Stage, pipeline and lifecycle stage list the stages you set up in their own settings, in that order, and a board can group by them.
- A deal's contact and company and a task's contact, company and deal are links to one record.
- Status, source and the dates Formspring sets itself are read-only.
Contact fields you added before
The custom fields you added to contacts before the data model (the ones listed under Contacts, then Custom fields) appear here as well. You can rename them, change the choices of a select, make them required, put them in another order and archive or restore them, and use them in filters, sorts, boards and imports. Their type and key cannot change, and an archived one stays archived rather than deleted, because segments and surveys may still use it. Segments, survey targeting and the API of contacts keep working with them unchanged.
Limits
Your plan sets how many fields an object can have. The data model page shows how close you are. Fields that Formspring adds itself (name, owner, dates) do not count.
