CiviCRM Community Forums (archive)

We're on 3.3.5 so things may be different these days ...

We work with many price sets attached to events.  We add new ones often, and need to keep the old ones so historical events have the right pricing info (for our reporting) - it seems if we change the prices in a price set, it affects all events that use that set, even old ones that have passed.  Therefore, management of price sets is getting out of hand with so many active ones.

But when we go to disable a price set, Civi doesn't let us - it says there are still active events using it.  However, the events we have, though active, are past (the start/end dates are old).

I was wondering why the check was on the inactive flag instead of the end date of the event?  Is there any data integrity reason for this?  Or would be ok for us to modify the manage price sets check to use dates instead of the active flag?

Or, alternatively, what happens if we make all old Events inactive (to then disable the price set)?  I was thinking that would somehow filter them out of standard reports and tools like "find participants" which we use often.  Actually, I guess I can test that out myself.

Thanks.