Currently there is no way to report or query details that are captured as event participant options. For example, if we capture something like dietary preferences in these fields on an NXT event registration form, there is no way to search for or query by everyone that has a certain value. Ideally, we'd be able to export this information also. Seems like a missed opportunity to capture details but have no way to manage it/view it in bulk.
N.B. I know we can export from a participant list but unfortunately, the participant list does not contain ALL details we would need to export for an event.
Yes please! It's ineffective to ask for information we can't use without 'improvising' an export method. Am assuming this will be the same for constituent forms, too, which makes them less than useful in that guise!
It's ridiculous that I can still query on Participant Custom Fields/Attributes that I can't even add or see in webview, but can't query on Participant Options which are webview only.
In fact, how are these even different things when they have the same basic function?!
I know you can see them in Lists and even export from there, but Lists don't provide all the other options/functionality of query.
This is imperative information to be able to export so that we can provide it as details behind their registration. For example, preferred tee time at golf tournaments; t-shirt sizes; and our list goes on-and-on.
This is a BASIC RULE in all data processing: if there's a way to put stuff into a system, there should be a [feasibly convenient] way to get it OUT.
Essential to view in a query: for each participant the answers they selected for each participant option. Not a query on participant options per se, but a query of participants
Yes, please! This is essential to capture participant options (the answers for each particpant, one participant
This is vital, the ability to view all information in one place. Please fix this.
PLEASE implement this. It is maddening needing to review this data manually for our events.
We are capturing information in the participant options fields and need to be able to view this in query.
This is a definite must! We use queries to pull all of our event participant information, and then use it in an export to access Primary Education information. We then have to give these details to people without Raisers Edge, so we need to be able to pull the event participant options (like dietary requirements) in the query and export
This is a MUST! Schools use these options to confirm alumni information (such as Class Year) to help identify alumni whose names have changed. Not being able to access this in Query makes it very hard to use for this type of thing.
Agree: Lists don't provide all the information we need, often, and our event coordinators want to be able to export these options, and/or query on them later. For example, I may want to query everyone who identifies as a current patient, and globally add a constituent code or action.