Yea, I've started using a work-around to temporarily code only the events that I want to export with constituent data (broader than what I could get from participant export). Since other than date (of which our org may have many events within a date or date range), event type is only other filter option, I added an entry to that table to use temporarily on event records I want to export for constituent exports. Normally, I would not recommend this kind of mis-use of a table, but it beats doing a lot of extra work with more data outside RE for those circumstances of using export for ad-hoc reporting or lists that just don't fit into a report that would manage that event selection for you outside RE. You have to remember to go back into the event after running the export to remove that type; and of course if your event actually has a type, then you lose that detail in the export (however at least that's all the same for any participant in the event so you could adjust that outside RE). I frequently segment event participations alongside other constituent indications, for example with searching for prospects for a specific initiative. Being able to have more options to select events during export would be great. I'll admit that for me the group field would not solve this, I support anything to help with the overall frustration of this for other organizations. A selection for specific event ID's or Names or records would be ideal, something akin to the campaign, fund, etc. filters available in gift outputs.

Seconded!

Selecting on specific events would be ideal. Otherwise, having been informed that the Start and End dates aren't actually a range at all(?!) how about giving both Start and End date fields range options (i.e. Start Date is between x and y, End Date is less than z, etc).

When I export multiple participations, I'd also love to be able to sort them by date order. Teams are forever asking us to output "the last event the supporter did" and that's just about impossible.

It would be great if you could filter by actual Event names/IDs within Export, similar to how you can do so with specific Constituent Codes, Solicit Codes, etc. If you want a list of Registrants invited to specific Events, and to show which of the specific Events they were invited to, that is currently not possible without dupes in a query list.

The workaround that we implemented was to simply use the Event Name as the Event Type. I think this limits us in other ways, but it is certainly the better of the two alternatives.