Smart field names tend to be written once, in a hurry, by whoever built the field: “Last Gift Amt 2,” “Mbr Exp NEW,” “Test – do not use.” Two years later that field powers a dozen queries, and when you try to give it a sensible name, Altru won’t let you edit it, or warns you about the queries that depend on it.
The reason is simple. Queries refer to smart fields directly, so Altru protects fields that are in use. A rename could break, or quietly change, saved queries, exports, and anything downstream of them. The protection is reasonable, but it means a cleanup that should take thirty seconds turns into a small project.
Here’s how to handle it without breaking the reports people rely on.
First, confirm what you’re actually blocked on
Altru’s behavior here can depend on your version and on how the field is used, so test before you plan. Open the smart field and try to edit the name. One of three things will happen:
- The edit saves. You’re done with Altru. Skip ahead to checking downstream exports and integrations, since those may match on the old column name.
- Altru shows a message about dependent queries. Note every query it lists. That list is your work order.
- The name field is locked with no explanation. Ask Blackbaud support whether names can be changed on in-use smart fields in your environment before you rebuild anything. It’s a five-minute question and it can save you an afternoon.
Option 1: Change the label in the query, not the field
Very often the person asking for a rename doesn’t care what the smart field is called in the field list. They care what the column header says in an export or on a report. If that’s the real problem, check whether your query’s output lets you set a custom column heading for the field. If it does, update the heading in each query that matters and leave the smart field alone.
This is the lowest-risk fix. Nothing about the underlying data changes, and you can do it one query at a time.
Option 2: Replace the smart field and repoint the queries
When the field name itself needs to change, say because staff pick it from the field list every week and the current name misleads them, the dependable method is to build a replacement and retire the original.
- Document the existing field. Record its type, parameters, filters, and any values it’s limited to. Screenshots are fine. You need to rebuild it exactly.
- Create the new smart field with the correct name and identical settings.
- Process the new field and compare. Smart fields have to be processed before they hold values. Once it has run, build a quick query with both fields side by side and check that the values match for a sample of records. A mismatch usually means a missed parameter.
- Repoint each dependent query. Open each one, add the new field, put it in the same position in the output, apply any filter that used the old field, then remove the old field. Run the query and compare the record count to before.
- Check selections and anything built on those queries. If a query is saved as a selection used by a mailing, report, or another query, test those too.
- Retire the old field. Once nothing references it, rename it to something clearly obsolete if Altru allows that now, or delete it. Before you delete, keep its process schedule in mind and make sure the new field has its own schedule set up.
A note on timing
Do the repointing outside of month-end, renewal mailings, or any report deadline. If one query gets missed, you want to find out on a calm day, not when finance is waiting on numbers.
Finding every query that uses the field
If Altru gives you a list of dependent queries, use it. If it doesn’t, you’ll need to search. Sort your query list by owner and ask each person who builds queries to check theirs. Shared queries used for recurring reports are the most important to catch. A personal ad hoc query that breaks is an annoyance; a broken membership renewal list is a missed mailing.
Keep a simple tracking sheet: query name, owner, whether it used the field in output or as a filter, and whether it’s been updated and tested.
Don’t forget what lives outside Altru
Exports are where renames hurt most. A CSV that feeds a spreadsheet, an email list, or a board dashboard often matches columns by header text. Change “Mbr Exp NEW” to “Membership Expiration Date” and the import on the other end may skip the column or fail entirely. Before you switch over, list every place a dependent query’s output goes and update the mapping there at the same time.
Preventing the next one
- Agree on a naming pattern for smart fields: what it measures, the time frame, and the unit, such as “Total Donations – Last 12 Months.”
- Use a description on each field to say who built it and what it’s for.
- Prefix experiments with something like “TEST” and delete them before anyone uses them in a shared query.
If your queries feed other tools
If you sync Altru queries to Google Sheets, Mailchimp, or ActiveCampaign, a column rename is a mapping change on that end too. Social Good’s Data Bridge syncs Altru query data to those tools, so after repointing a query you’d review its field mapping in one place instead of fixing a manual export file by hand.
