Attribute Field Types: Every Field and Where It Works
Reference for every BackOps attribute field type, from Text and Select to Crew Member pointers, with what each stores and which records support it.
Every attribute in BackOps has a field type that decides what it holds and how it is filled in. The field type is chosen when the attribute is created in its library and cannot be changed afterwards, because values already entered depend on it. This page lists every field type and which kinds of record support it.
Field Types
| Field type | Holds | Notes |
|---|---|---|
| Text | One line of text | Up to 500 characters |
| Rich Text | Formatted text | No length limit |
| Number | A number | |
| Date | A calendar date | Can anchor a relative due date on event types |
| DateTime | A date and a time | Can anchor a relative due date on event types |
| Checkbox | Yes or no | |
| Link | A web address | Up to 500 characters |
| Select | One option from a list you define | The attribute carries its options |
| Multi Select | Several options from a list you define | The attribute carries its options |
| File | One uploaded file | |
| Multi File | Several uploaded files | |
| Collaborator | One collaborator from your organization | A link to the record, not a copy of its name |
| Multi Collaborator | Several collaborators | |
| Crew Member | One crew member from your organization | A link to the record, not a copy of their name |
| Multi Crew Member | Several crew members |
Select and Multi Select values are saved as the chosen option, not as its text. Editing an option's wording, where the attribute editor allows it, keeps every saved value pointing at the right choice. A value that names no current option is dropped rather than saved.
Which Records Support Which Field Types
| Field types | Events | Crew | Collaborators | Locations | Resources |
|---|---|---|---|---|---|
| Text, Rich Text, Number, Date, DateTime, Checkbox, Link | Yes | Yes | Yes | Yes | Yes |
| Select, Multi Select | Yes | Yes | Yes | Yes | Yes |
| File, Multi File | Yes | Yes | Yes | Yes | Yes |
| Collaborator, Multi Collaborator, Crew Member, Multi Crew Member | Yes | Yes | Yes | Yes | No |
Resource attributes do not offer the collaborator and crew member field types. Resource attributes can instead drive pricing, as variants, price modifiers, or units; see resource types and attributes.
Choosing Between a Pointer Attribute and a Role
On an event type, a Crew Member or Collaborator attribute and a role can both point at a person, but they are not interchangeable. A pointer attribute records a fact, such as who the client contact is. A role names a part on the event, such as Production manager. Effects can act on whoever fills it, for example by notifying them or adding them to the event, and an event type can make a role the default assignee for tracked details. When something should happen because a person is in a slot, use a role. See roles and effects.
On event attributes and event roles, an organization admin can limit which crew members or collaborators the picker offers, for example only your account managers.
Project management has its own task attribute library with the same field types. Task attributes are not arranged on types or in sections: each one applies to every task in the organization. See project management.