Default event fields: one field for every event
Default Event Fields let you define a field once for your organization, such as “Dietary restrictions” on Contacts, and have every event get it as an ordinary event field. Each event keeps its own answers. New events get every default automatically, and you choose whether events that already exist get it too.
Why use it
Section titled “Why use it”Teams that run many events often rebuild the same custom fields in each one by hand, and the copies drift: a renamed option here, a missing field there. A default event field is created the same way in every event, stays linked to the default, and can be changed in one place. Unlike a global field, its answers stay in each event, so a speaker’s dietary needs for one conference never overwrite another’s.
Open Default Event Fields
Section titled “Open Default Event Fields”Open Organization Settings, then Library → Default Event Fields. The page lists every default with its Name, Record (Contacts, Groups or Sessions), Type, how many Events have it, whether it is Locked or Editable In events, and when it was Updated. Search the list by name.
Adding, editing and deleting defaults takes the organization permission Manage global fields. Members without it can see the list but not change it.
Add a default field
Section titled “Add a default field”Click Add default field and choose Contacts field, Groups field or Sessions field.
Give the field a name and choose its type and options, as you would for any custom field (see Create and delete custom fields). The field is always created as an event field in each event.
Turn on Lock in events if event admins should not change it. They can still hide the field in their event, but they cannot edit or delete it. Leave it off to let each event adjust its copy.
Save. Every event created from now on gets the field.
Add it to existing events
Section titled “Add it to existing events”New events get a default automatically; existing events only get it when you ask. From the default’s Actions menu, choose Add to existing events, then pick Which events:
- Upcoming and ongoing events
- All events, including past ones
Before anything is created, a preview shows what will happen:
- how many events get a new field;
- how many already have a field with the same name and type: that field is linked to the default, not duplicated, and keeps its answers;
- how many have a field with the same name but another type: those events are skipped, so nothing is overwritten.
Click Add to N events to go ahead, or Only new events to leave existing events alone.
Change a default
Section titled “Change a default”Choose Edit from the default’s Actions menu. When you save a change that would affect events that already have the field, Sessionboard asks Apply to all events? and says how many event fields would change:
- Save default only changes the default, so only events created from now on get the new version. Existing event fields stay as they are.
- Save and apply to N events updates every event field made from the default. Options are only added or renamed, never removed, so answers already given are kept. An event that already has another field with the new name keeps the old name, and the dialog says how many.
See which events have it
Section titled “See which events have it”Click a default’s event count, or choose View events from its Actions menu. The list shows each event, its Event ID, when it Starts, the Field name in the event, and whether the field Matches the default or was Changed in the event. Search, sort, filter on Field, and export the list.
Every change to a default, and every event it is added to, is recorded in the field’s history.
Delete a default
Section titled “Delete a default”Choose Delete from the default’s Actions menu, then Delete default. New events stop getting the field. Event fields already made from it stay in their events, with their answers, as ordinary event fields.
