Create custom event fields

Creating custom fields means including, in your events, categories of information that don't appear by default on the Trumba® Event Information form (the form that appears when you add or edit an event). Using published fields that are customized for your events can help visitors to your published calendar find what they're looking for more quickly.

Custom fields used internally can also help calendar editors keep each other up-to-date. For example, you can include fields for who created and last edited an event, revision history notes, and so on. By choosing not to publish these fields, you can keep them from appearing in your live calendars.

To create new custom event fields (for accounts created before October 5, 2010)

1. In your Trumba account, under Other Tasks, click Define custom fields, and on the Define Custom Fields page, click Create a new field.

   On the Define Custom Fields page, what does Edit Custom Field Overrides mean?

2. On the Create a New Custom Field page, in the Field Name section, for Field name, type a name for the new field. (When you're choosing a name, remember that field names show up on your published calendars.)

   Type a description if you want. This is useful primarily if more than one person will be adding events to your calendars and you want to provide guidance.

3. For Field type, select the type of field you want to create.

   Can I see some explanations of what the various field types are?

4. For all field types, you see the following options:
   • Default value If event creators will typically use a certain value for the field, type or select a default value. Otherwise, leave Default value blank.

     For example, for an age range field, if most of your events are targeted at a specific age range, you might want to make that age range the default.

   • Value required If you want to ensure that the field has a value in every event that's created, select Yes. Event creators who don't provide a value will see an error message when they try to save. Otherwise, select No.

     For example, you might require a value for an Event Type field because calendar visitors will be able to filter events by type in the published calendar.

5. The other options you see depend upon the type of field you're creating. For example:
   • For a single line of text field, you can specify the minimum or maximum number of characters the field can contain.
   • For a List of choices field, you're asked to name the list and add the value choices the list contains. For example, if you create an Audience list of choices field, possible value choices might include Adults, Teens, Children, and Seniors.

     You also see a couple of additional options:

     • Select multiple values For an Audience field, you might select Yes to allow event creators to indicate that an event is appropriate for multiple age ranges. For an Event Type field, on the other hand, you'd select No since events can be of one type only.
     • Display style Decide between displaying the list of choices values inline (as check boxes or radio buttons, in a drop-down list, or as an auto-complete field that displays values as event creators start typing.

       I'd like more detail about the list of choices display style options.

6. Under Include in Templates, from the Templates drop-down list. select the templates in which you want to include the field.

   Tell me more about event templates.

7. For Visibility, two options are selected by default:
   • Allow this field to be published means that the custom field will be publicly displayed in events on your website calendar.

     Tip If you're creating a custom field for internal use only, clear this option.

   • Show this field on the event submission form means that, if the public event submission form is enabled on your account, this field also is included on that form.

     I'd like more information about letting calendar visitors submit events.

8. Click OK.

Tip In some calendar views, you can change the way fields are displayed. Learn more.