Override custom field values in specific calendars or event types

When you create custom fields for your organization's events, you might want to set a default value for the field, but the value changes depending on the calendar or event type in which the field appears. By using custom field overrides, you can set different default values for custom fields according to the condition in which the fields are used, including:

• Only when the fields are used in particular event types.
• Only when the fields are used in events owned by particular calendars.
• When the fields are included in particular event types only when the event types are used on particular calendars.

For example, the picture below shows events at different branches of a city's public library. Instead of setting a default value that's global to the Trumba account, the default value is set for each calendar.

For any field, you can set conditional overrides whether or not you set a global default value when you create the field.

To specify when to override a custom field's global default value

1. In your Trumba editing environment, under Other Tasks, click Define Custom Fields.
2. In the Define Custom Fields page, click Edit Custom Field Overrides.

   

3. On the Edit Custom Field Overrides page, set the condition in which you want the value to change:
   • When the field appears only in a particular event type that uses the field (regardless of the calendar), select the event type from the Event type drop-down list, and for Calendar leave All Calendars selected.
   • When the field appears in any event type but only on a particular calendar, for Event Type, leave All Event Types selected, and select the calendar from the Calendar list.
   • When a particular event type uses the field only on a particular calendar, select both the event type and the calendar.

   The fields that match the Event Type and Calendar conditions appear in a table. Why are there some values in gray?

4. For each field, do any of the following:
   • Enter a new default value for the selected condition.
   • Select the check box in the Required column to make a value required for the field in the selected circumstances.
   • Under Other Settings, enter the minimum or maximum number of characters (for text fields) or values (for numeric fields); enter new values for drop-down lists, and so on.

Gray field values indicate inheritance

The Edit Custom Field Overrides form shows inherited default settings in gray. For a selected condition, a field can inherit:

• A global default value.
• A default value set in a condition that is a superset of the selected condition.

  The following picture shows how the inheritance hierarchy works. Below the default (global) condition, each condition is a subset of the previous one.

You can override the inherited value by entering a new value, and you can revert the field back to inherit from its direct "parent" by clicking the inheritance button next to the field ().

• If a global default value hasn't been set, the value is blank, and you can either leave it that way or enter a value that appears only in the selected condition.
• If you have set a default value for the field under a different selected condition, that value might also appear in gray. If you change the global default, you can reset it to the default by clicking the

• When you're done with the settings, you can set custom field overrides for other event types or calendars (or combinations of the two), or just click OK to return to the Define Custom Fields page.