Event organizers, we've got great news for you! 😃

You no longer have to recreate a custom content field for each event. For people, exhibitors and sessions, you only need to set your custom fields once per community. 

For each event within the same community, you can display or hide any custom field previously created for other events.

How does it work ?

You can now share fields between events within a community. Organizers need to create fields only once per community and can then decide if they want to enable or disable it for any event in the same community.

All fields are still created at the Event level, but can be reused for another event in the same community.

👉👉Default custom fields

On any content setting, all content (people/exhibitors/session) will have a unique default custom field per community:

• 1 type for all the event's people
• 1 type for all the event's exhibitors
• 1 type, 1 location, 1 topic for all the event's sessions

⚠️ When this update is released, what will happen to all the default custom fields for existing events?

Let's look at an example:

BEFORE the release we have Event 1 and Event 2 in a community.

There is one type field on Event 1 with:

• Value 1
• Value 2

There is one type field on Event 2 with:

• Value 3
• Value 4

AFTER the release, we will have a unique type for Event 1 and Event 2 that will have the following values:

• Value 1
• Value 2
• Value 3
• Value 4

👉👉Other custom fields

• It is still possible to create a custom field, but it will only be enabled for the event where it has been created. The custom field can be enabled for any other event in the same community afterwards.
• In the search bar, you can search for any existing field for any event in the same community. Click on the relevant field and it will be added to the current event. See the following example:

You will notice that in the search results, you can see which event each field is enabled for.

⚠️ Please note that deleting a field, deleting a field's value, or reordering a field's value can impact several events. This is why an alert will popup when an organizer is taking one of these actions. See the following examples:

- Deleting a field permanently ('delete from all events' button):

- Deleting a value field:

- Changing the order of the values: