Keep event registration invoices when actual event is deleted
I deleted an event from past. Now I have hundreds of "overpayment". What is the best way to address these overpayments? In the future, can the event details and the financials somehow run independent of each other so we dont have to keep an bunch of past events?
Hamnerja
shared this idea
-
Dmitry Buterin commented
As of now, the only reason I am aware of to delete past events is to keep the total event list smaller/manageable to search currently active events. I think the best solution for this is to provide better filtering/searching capabilities - see http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8827291-managing-a-database-with-many-events-5687
If there are other reasons for deleting past events, I would appreciate input here.
-
Can you elaborate - why wouldn't you want to keep past events? Deleting theme deletes event registrations etc.
