Sooner or later every Altru administrator hits the same wall. You’ve built a query that finds exactly the 1,400 records you need to change, you go looking for a global change that will update them all at once, and it isn’t there. What follows is usually an afternoon of clicking through constituent records one at a time.
This article covers where the gaps tend to show up, how to confirm what your own database can and can’t do, and the workarounds that hold up when the process you need doesn’t exist.
What global change in Altru actually covers
Altru does include global change processes. You select a set of records (usually a selection built from a query), pick a process, set parameters, and run it. The catch is that the list of available processes is fairly short, and each one changes a specific, narrow thing. It is not a general “update any field on any record” tool.
That design is deliberate. A bulk update that can touch any field is also a bulk update that can wreck a database in one click. But it means the processes you get are the ones Blackbaud chose to build, and plenty of everyday cleanup jobs fall outside them.
Because the exact list can differ as Altru is updated, don’t rely on anyone’s memory of it, including ours. Open the global changes area in your own database and read through what’s offered before you plan a cleanup project.
Where administrators most often come up short
These are the kinds of bulk changes Altru admins commonly look for. Some may be partly covered in your database; many are not covered at all, or only in a limited way. Check each against your own list before assuming either way.
- Constituent fields beyond the basics. Things like contact preferences, solicit codes, constituent codes, or custom attributes across a large group, especially adding one value while leaving others intact.
- Removing or ending values in bulk. Adding is often easier than taking away. Clearing an outdated attribute or ending a code on hundreds of records is a frequent pain point.
- Address and contact cleanup. Marking addresses or emails as invalid, changing a primary flag, or standardizing formatting after a returned mailing.
- Membership record adjustments. Shifting expiration dates for a group (after a closure, for example), changing a level, or correcting a program assignment.
- Household and relationship fixes. Re-pointing or cleaning up household relationships after an import went sideways.
- Revenue-side corrections. Changing a designation, appeal, or similar coding on many existing payments. These are sensitive because they affect finance reporting, so expect limits here.
How to confirm whether something is possible
- Read your global change list carefully. Process names can be broader than they sound. Open the parameters of anything close to what you need.
- Test in a sandbox if you have one. Run the process against a small selection and check the results on a few records before going wider.
- Check the import options. Some changes that have no global change can be done by importing updated values onto existing records. Whether a given field can be updated this way varies, so test it.
- Ask Blackbaud support. Describe the field and record type exactly. They can tell you whether a supported route exists, which is better than a guess from a forum thread.
Workarounds when the process doesn’t exist
Import onto existing records
For many constituent-level updates, the most practical path is to export the record IDs from a query, add the new values in a spreadsheet, and import them back as updates. Keep the file small for the first run, and save a copy of the original values before you start so you can reverse the change.
Batch the manual work
When nothing automated is available, make the manual edit as fast as possible. Build a query that returns exactly the records left to fix, add it to a selection, and work through it. Re-run the query as you go so finished records drop off the list. Split it across staff with a clear rule about who takes which part.
Stop creating the problem
A lot of global change demand comes from the same mess being made repeatedly. If you keep needing to fix a code that staff apply inconsistently, or emails entered with errors at the desk, spend some of the effort on the source: tighter data entry instructions, fewer choices in drop-down tables, and a recurring query that flags new bad records each week while the list is still short.
Decide what you can live with
Not every field needs fixing. If an outdated value doesn’t affect mailings, reports, or benefits, it may be cheaper to exclude it in your queries than to clean it up. Spend manual time on data that drives decisions or reaches members.
Before you run any bulk change
- Save the selection and the query criteria, with a note on why you ran it.
- Export the current values for the affected records so you have a record of what changed.
- Run on a handful of records first, then check them on the constituent record itself, not only in a query.
- Avoid running large changes during busy sales hours, when staff are working in the same records.
Quick answers
Can I write my own global change in Altru?
Altru is a hosted product, and custom processes are not something administrators typically build themselves. Ask Blackbaud support what options exist for your account.
Is importing safer than a global change?
Not automatically. An import can overwrite good data just as fast. The advantage is that you control the exact values in the file, so keep a before copy and test small.
