Why cant I query participants over multiple events?

When using a Participant query with criteria that looks for the same participant records over multiple events, the results show 0 records found, but the same constituent name can be seen on the Participants tab of each event being queried.  Example scenarios include looking for participants who have been added to a list of specific event records, or looking for participants who have registered for one event but not for another event.

Why is the query not working?
A Participant query cannot be used to look for the same participant record over multiple events.  This is because each participant import ID value is unique, so a constituent who is part of five events will have five unique participant import IDs.  Query is therefore unable to match these five different values to the same constituent record and treats each participant import ID as a separate record.  This also means using merge queries will not work when this query type is used.

Alternative solutions:
1. Use a Constituent query, which matches the constituent record to the event using the same constituent import ID value.
    (Note: Any event participants who do not have a constituent record of their own will not be included in the results.)
2. Create a Participant query for each individual event record, then export these into Excel and sort/compare manually.

Steps to Duplicate

1. In The Raiser's Edge, create two event records and add the same constituent to both.
2. Create a Participant query with any criteria that includes searching over more than one event.
    eg. Event ID one of <EVENT1>, <EVENT2> with 'Each record must meet all specified criteria' ticked.
3. Add any appropriate output/sort fields.
4. Run the query and note no results appear.


 Raiser's Edge

Was this article helpful?

Thanks for your feedback! Did this solve your issue?

Comments (optional):

Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):

Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.