I just added this Idea and assigned you as the creator, so you should have gotten a notification about this. Here's the direct link: https://renxt.ideas.aha.io/ideas/RENXT-I-3545!

Hi Samantha,

Have you created a new idea about re-using options across events or should I go ahead and create it?

Regards

Bolaji

We track how participants hear about some of our events across events, to determine the top-performing communication/advertising channels.

Also, we re-use the same options for our challenge events because those are the options that are always available. For example, running vest sizes, cycle jersey sizes, t-shirt sizes, accessibility requirements, participant's method of signing up for the event, participant's minimum sponsorship status, etc.

So having the ability to re-use the same options or copy those options from one event to another would be great. We are currently not using 'Events' in NXT because of this, we have instead decided to stick to using 'Events' in the database view till we can re-use options in NXT.

Thank you for the additional detail! You can either add this as a separate idea, or, I'll check first thing next week and I can create a new idea for you with these details.

I'm curious about the reuse between events. I've definitely heard that customers sometimes have the same sets of options needed from event to event and we are looking at how we could potentially have a default set of options automatically included across events, or include it in a future event "copy" or event templating process. You mentioned data inconsistencies...are you reporting on any attributes today across events where consistent data is important? Or are you still only looking at the selections a participant makes for a participant attribute at an event level, but want to have those attributes presented consistently to those users across events?

--Samantha

Hi Samantha,

The limitations of the participant options which you have outlined, makes it difficult for us to us the participant options. Having to set up options per event is time consuming and opens up opportunities for a lot of data inconsistencies. An improvement of the participant options to function like custom fields (attributes) will be most useful.Does this need to added as a separate idea?

Hi! Thanks for submitting this Idea!

Have you tried out our Participant Option feature in webview? This is a more flexible way to capture additional participant information like those you mentioned - dietary preferences, accessibility requirements, etc. You can customize all the options and selection values per event. This allows easy reporting right from the Event record for response totals, so it's easy to see how many "Chicken" meals you need and which participants selected that option. You can set these up on the Event record itself in Web view on the Participant Option tile.

There are some downsides to this - in order to improve on how these are managed, you set them up per event and they are NOT attributes. Therefore, if you need to report out of these or see them on a registrant record in database view, they will not show up there as they are webview only. Also, only the NXT event registration form allows you to collect these, so if you're still using Online Express or BBNC for online registration, you may want to stick with participant attributes, even if they are webview only.

Take a look and let me know if you think Participant Options works for you. At this point we are not planning to add participant attributes as they exist today into webview and Participant Options is our solution for this, so I'm going to mark this Idea as already exists.

Thanks,
Samantha McGuin
Principal Product Manager