Deleting an event in Altru is easy right up until the event has anything attached to it. An event you created by mistake ten minutes ago will usually go away cleanly. An event that has sold a ticket, taken a registration, or been touched by a refund usually won’t, and Altru will tell you so with an error rather than a helpful explanation.
That’s by design. Altru protects anything tied to revenue, and once money has moved, the record has to stay so your financials, batches, and reports still add up. So the real question is usually not “how do I delete this?” but “what should I do with an event I don’t want anymore?” The answer depends on what kind of event it is and what’s already connected to it.
First, figure out which kind of “event” you mean
Altru uses the word “event” for two different things, and they behave differently:
- Scheduled program events. These are the dated, timed instances of a program you sell through daily sales or advance sales: a 10:00 planetarium show, a Saturday behind-the-scenes tour, a timed-entry slot. They usually come in batches, generated from a program schedule.
- Special events. Galas, member nights, fundraising dinners, and similar one-off occasions with registrations, registration options, and often invitations and expenses attached.
Both can be deleted when they’re empty. Both get harder to remove the more they’re connected to constituents, orders, or revenue. Knowing which one you’re dealing with tells you where to look for the blocking records.
When delete works
You can generally delete an event when it has never been used: no tickets sold, no registrants, no payments, no refunds, no reservations from group sales. Typical examples:
- A duplicate event created by double-clicking or rerunning a schedule.
- Program events generated for the wrong date range or the wrong times.
- A special event set up as a draft that never went live.
For these, open the event record and use the delete action. For a run of bad program events, check whether you can remove them in bulk from the program’s list of scheduled events rather than one at a time. Bulk options vary by role and version, so if you don’t see one, it may be a security setting rather than a missing feature; your Altru administrator can confirm.
When delete is blocked, and what to do instead
If Altru refuses, something is pointing at that event. Before trying to force it, ask whether you actually want it gone. In most cases you don’t; you want it out of the way.
The event is canceled or rescheduled
Keep the event, handle the people attached to it, and then take it off sale:
- Pull a list of everyone with tickets or registrations. A query on orders or registrants filtered to that event works well, and gives you emails for the cancellation notice.
- Process refunds or exchanges the normal way so revenue and batches stay correct. Don’t edit payment records to make an event “empty.”
- Once nobody is holding a ticket, remove the event from sale: close it for online and on-site sales, set capacity to zero, or mark it inactive or canceled, depending on which options your setup exposes.
- Rename it with a clear prefix such as “CANCELED” so staff don’t sell into it by accident and it’s obvious on reports.
The event happened, but it’s cluttering lists
Old events with real sales should stay. They’re your attendance and revenue history, and deleting them (even if you could) would leave gaps in year-over-year reports. Filter them out of the views and queries staff use day to day instead.
It was a test event that got a test sale
This one is common. Someone ran a practice transaction against a real event and now it won’t delete. Refund or reverse the test transaction through the normal process, and check whether any batch containing it has already been committed. If it has, talk to your finance contact before doing anything else; reversing a committed test sale is a finance decision as much as an Altru one. After the transaction is fully cleaned up, try the delete again. If it’s still blocked, take it off sale and rename it, which gets you most of the way there.
Check these before you delete anything
- Web forms and website calendars. If the event or its program is linked from a web form or embedded calendar, removing it may leave a broken link or an empty date on your site. Update those first.
- Queries and smart fields. Saved queries that filter on a specific event can quietly return nothing after it’s gone. Not harmful, but confusing in a monthly report.
- Group sales reservations. A group booking tied to the event will block deletion, and the group contact needs to hear from you anyway.
- Special event extras. Invitations, tasks, coordinators, and expenses on a special event may need to be removed or reassigned before the record can go.
If you’re still stuck
The error message usually hints at the type of record in the way, even if it’s phrased in database terms. Note it exactly, then look at the event’s tabs for anything that isn’t empty. If you can’t find the cause, Blackbaud support can tell you which linked records are blocking it. If you have a sandbox, try the same cleanup there first, especially for anything involving refunds or committed batches.
And if you find yourself deleting mistaken program events every season, the fix is upstream: review the program schedule settings before generating events, and generate a short range first to confirm dates and times look right.
Quick answers
Can I delete an event that has sold tickets?
Generally no. Refund or exchange the tickets, then take the event off sale and mark it clearly. The record stays for financial history.
Will deleting an event delete the program?
No. Deleting a scheduled event removes that one instance. The program and its other dates stay. Confirm in a sandbox if you’re removing many at once.
Is there an undo?
Not that you should count on. Treat deletion as permanent, and when in doubt, deactivate instead.
