Add ability to query or report on event participant options in RE NXT Web View

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.

  • Megan Girvalo
  • Jan 23 2025
  • Reviewed: Voting Open
  • Attach files
  • Joanna Clarkson commented
    15 Jan 12:14

    This is vital, the ability to view all information in one place. Please fix this.

  • Marco commented
    November 05, 2025 14:38

    PLEASE implement this. It is maddening needing to review this data manually for our events.

  • Therese Junker commented
    September 23, 2025 17:13

    We are capturing information in the participant options fields and need to be able to view this in query.

  • Abby Hallett commented
    September 16, 2025 12:30

    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

  • Christine Robertson commented
    September 02, 2025 15:28

    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.

  • Tracy Hernandez commented
    August 15, 2025 18:47

    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.