The alternative solution on knowledgebase - "In order to delete participant records, we must open the event record and go to the Participants tab. Open up each participant record and delete them manually." isn't really of any use when there are a few hundred participants that you need to delete from the event!

Absolutely. With what I know about the table structures behind RE, it doesn't seem like this should be a major headache for Blackbaud from a development point of view. There's already the ability to create a participant query - it shouldn't be hard to add the ability to globally delete these participants.

It would be very helpful to be able to delete multiple participants at a time. Thanks.

it's sooooooo........ painful at present to delete the record one by one. So yes, globally deleting a group of participants shouldn't be treated any differently to any other global delete.

I'm really surprised we can't do this. Since it is also impossible to migrate participants from one event to another, it's pretty poor that we can't even globally delete them from the wrong event.

Blackbaud's suggestion to us was that we globally add participants to the correct event, then delete the old event. This doesn't work for us for several reasons:
1. We don't want to delete the old event - it is still a legitimate event with legitimate participants.
2. We can't globally add the participants to the new event, as their participant fields and attributes are variable - we can use an import file, but we still have to manually delete them from the old event. In our case, that means 88 manual deletions - but I can easily imagine a case where an organisation might have hundreds or thousands to delete - mistakes and changes happen, and that's what Global Delete is for!