Addressees/Salutations Clean-up
Comments
-
Have you looked at non-constituent records or Event name tags? I do believe this could be the problem.2
-
If it's not as Jenny Stephens replied, could it be that it was format selected and then the 'editable' box was checked? If so, that about makes cleanup impossible.1
-
I moved this discussion to the Raiser's Edge forums. Thanks!2
-
Suzi, if you create a new constituent query and click the Find binoculars, there are many instances of Addressee/Salutations (spouse, contacts, organizations, individuals, etc.) so I think you may need to include more fields in your query to find the ones you want to delete. You would also need to check through the Specific Addressee/Salutation fields to find them.
Also, Crystal Bruce, I see that you moved this discussion to the Raiser's Edge forums, but without a link, I'm not going to try to find the right place to post my response - sorry!1 -
Thank you all for your responses. I'm refreshed to see this.
Linda Burns - yes indeed! All of the varying options have certainly been touched upon within this very deep process. I have queried as many options as I could find to then use in the global replace process so that I can then delete the ones I want...to no avail. That's why I'm finally here. Thank GOD I have some slow/project time to get a second wind and go back to this. Thank you.
JoAnn Strommen - I actually queried those with editable = yes to eliminate that from hindering the process. Still didn't work. (I've been shocked as I've unturned so many of these 'stones'.) Thank you!
Jenny Stephens - Thank you. I did relationship queries in this process so that should cover the non-constituent records, right? We haven't used event name tags. Good considerations.
COUPLE QUESTIONS:
1) Have any of you tried this process and been successful?
2) Since the various articles in Knowledgebase that have steps to follow did not fully get me there, what do you all think of the question I posed to developers: Why can't the clean up process of querying the addressee/salutation that one wants to delete from these various fields all be part of the steps, and then finally include a step where the user can delete the addressee/salutation 'at their own risk' be an option? Once it's deleted, if there is some very hidden area where the addressee salutation is being used, it wouldn't be hard to choose another. And there could be sidebar instructions showing how to query any addressee/salutations that are blank and using global add to insert an active choice? In each of your individual database/work scenarios, do you see this possibility being a problem?
Thank you all!!0 -
I don't see a problem with the solution you're posing. If you have a link to a sugestion that I can vote for it, I'll gladly do so.2
-
Awesome Linda - I will look into how to share the suggestion! I'll let you know when it's out there. Thank you! ~Suzi0
-
This is a fundamental issue with the way RE was designed. Specifically, there's no way to effectively query non-constituent data, whether that be spousal/relationship or contact or even event participant data. So, I don't know what can be done here.
However, you can find this information if you are patient. I have a query that I found on these boards many years ago (I can't find it right now, but I printed it out somewhere at the office). Keri Barnhart goes through the gist of it in great detail here. My query is similar, and has about 30 something conditions.
https://community.blackbaud.com/forums/viewtopic/147/50910?post_id=197749#p197749
Regardless, it can be done. I wish you good luck and godspeed with it. It's a taxing process, but the beast can be slain.4 -
Wowwwwww Dariel! Thank you SO MUCH! I can't wait to dig into this! Thank you for the assistance to slay this beast!! ? I truly appreciate it. Wonderful-Wonderful-Wonderful!
Best regards,
Suzi1 -
Thanks for tagging me in, Dariel! I've been swamped these last couple weeks and haven't been keeping up on the Community forums.
I can say that I have been (mostly) successful at cleaning up my name situation. I never got around to cleaning out the worst of the crud on the most obscure records before moving to a new organization, but at that point, I was doing more manual search and change, so it was only a matter of time.
Suzi, I don't know if this will be useful for you, but because I had such a headache trying to get help a couple years ago for the project, I'm in the habit of sharing the relevant details to active threads to help other folks now or using search in the future.
I find that it's helpful to define the terms you're using for this project:
Add/Sal = full set of data fields applied to a record that include A) the TYPE andthe DISPLAY
Formula = the combination of data parts that create the Addressee/Salutation entry in the Add/Sal Configuration and are used to create the DISPLAY
Type = the configurable table of labels that can be assigned to aid in data processing (Primary Addressee, Thank You Note Salutation, Name Tag Name, etc.)
Display = the result of the formula, accounting for variable data on a record
Editable = the checkbox that allows overwriting of a display name has been activated, most likely because none of the formulas fit
There are several places where either the Addressee/Salutation elements live or where they are used to pay attention to. As far as I remember, this is a complete list:
1. Add/Sal *Formula* Configuration
2. Add/Sal Type Table
3. Constituent Add/Sal Tab
4. Relationship 2 tabs for individual and contact non-constituent relationships
5. Membership "Name on Card"
6. Event "Place Card" and "Nametag"
7. Default Sets
8. Import-o-matic rules, or other data entry tools you may use
9. BBNC defaults
10. All output configurations (Report and Mail parameters, Query and Export criteria/output)
When doing a clean-up, the goal is to remove redundant formulas, assign the correct formulas to one or more types, and ensure that the table data feeding into the display is correct. You will then need to check that everything which uses the formulas or references an Add/Sal is pointing to the correct type(s), and that no old/redundant ones are being called by your data entry tools.
What I found is that the most difficult place to do cleanup - where the Global Change and Imports resist efforts - are in the Membership and Event records. The interface for choosing a name display for nametags, placecards, and membership cards is different from everywhere else. It uses a drop-down menu that first calls on any assigned Add/Sal from the constituent record, then lists all of the display results of the various formulas. In every other place in Raiser's Edge, you are able to choose either the Type or the Formula, rather than both Type AND Display.
When you attempt to delete a formula from the config table, you will get a message specifying Event or Membership if the formula is being used in one of those places. If it's just a generic "this is present on a record", it's attached to a constituent, individual relationship, contact, or it may be present in one of the output options, or in a Default Set.
For this reason, I recommend first establishing the good. Set up what you want an ideal record to include in terms of add/sal, both the formulas and the types, and where you would use each type. Update your records to be good. Then go in and clean out the stuff you don't want - you'll get rid of some headaches that way.
Some of the tips I have for cleaning out the crud and maintaining a clean add/sal structure:
- when choosing a Membership or Event display name, if you leave the field blank before choosing the Editable option, it will NOT associate with a specific formula/type. However, if you chose an item from the table, then make it Editable, that formula and type will be "locked", and you will have a fine time tracking it down.
- on Constituent or Relationship records, if you choose from the formula list, then make the display editable, the underlying formula is NOT locked.
Example:
* Formula - #52 in config - [Title] [First] [Middle Full] [Last] [Comma] [Suffix]
* Mr. James Alexander Jones, III wishes to be addressed as Mr. J. Alexander Jones, III
* The suffix table already includes a comma for numeral suffixes
* The display based on this formula is Mr. James Alexander Jones, , III
* If you mark it editable and revise it to shorting the first name and remove the extra comma, it will still be associated with #52, but that association will be hidden. You can't delete #52, because it's being used.
* However, if you were to globally change all #52 formulas to #53, which does not include an extra comma, the editable Add/Sal will now be associated with #53
* You can test this by marking the display not editable again - it will revert to the drop-down menu, but will be the new formula.
- It is not possible to merge add/sal formulas, as much as we wish we could.The work-around is to globally change one formula assignment to another, then attempt to delete the one you don't want. If you can't, that formula is being used in a Membership or Event. Adding extra, unique text to the beginning of the formula will help you find any non-editable instances via query. Then, you can look at all editable Membership and Event name displays to check what the underlying formula is.
Depending on how extensive your Event names are used, you might find that it saves time to export all editable nametag/place card data, delete all nametag/place card data, then re-import the original data on top of the blank in the drop-down.
For Membership...you can't change the name on card for memberships which are in Dropped status. And once you change the Name on Card, it applies retroactively to all previous membership transactions. I would simply reset the default membership name on card, then look at the Editable ones to manually comb through.
When it comes to relationships... keep in mind that these are often multi-level. If you take care of your constituents' names first, you can then leave them out of future clean-up queries on individual and contact relationships, which will save time. Spouse is a type of individual relationship with a few upgrades that make it a little easier to adjust the add/sals for them.
----------------------------
My big wish for the developers is to fix the way membership and event names work! They muck up a lot of the process and make things very difficult.
I would also like to have an in-the-background merge option for the add/sal formulas.
Finally, it would be nice to be able to easily query ALL add/sal related fields by which data parts contribute to the display without having to look up the formula configurations or go through export/import.
Oh, and if i'm doing a Relationship query, please let me open the relationship record from the results!!! At my last org, I had identical Relationship and Constituent queries running, but some records showed on one but not the other. It was very strange and no one could tell me why. (It seemed to be artifacts of an old conversion of data from a decade previous, but we weren't 100% sure.)8 -
Keri Barnhart You ROCK!!!!!!!!!!!!
Thank you so much for all of this detail now and from your previous post ?2 -
For what it's worth, one of the thing that frustrated me the most is this part of your original post:
THEN when you go to delete it, it states it cannot be deleted because it is still found in records. You next need to ensure you are checking that any relationships do not have the addressee/salutation - query that; do the global change... But it still says it's in a record. Is there anyone out there who has gotten through this particular clean-up successfully?
If attempting to delete the formula gives me an error saying "No! Do you really want to break something on one of your many users right now? This is still in use!" warning, why can't the error message also pop out the list of associated records? Is it too processing intensive or something? It would save so much headache for so many of us... and not just for these configurations, but all the tables. We had some oddities leftover from that conversion issue where we literally could not find an instance of a particular table entry anywhere - and NXT didn't think it existed and wouldn't give it as an option in the relevant drop-downs! - but RE wouldn't let me delete it.
But unless your database is also haunted by echoes from an earlier upgrade/conversion, any time you see that message for addressee/salutation related things, it's probably because RE is finding it in one of the places I listed above. Getting creative with how you suss out Editables and using Global Change to point assigned Types to a different-but-similar formula can make a big difference quickly!
And another caution - be careful that if you do have a lot of Editables, you're looking at why before you delete or change them!
Is it because users couldn't get into config to create new formulas, and a lot of constituents go by a nickname? is it because of mismatched commas with suffixes? That can help identify formulas you need. It can also help identify if the rules for deceased spouses or people changing their names need to be cleared up. We had a number of women whose names were made editable apparently because some users couldn't update the name data fields but COULD change the add/sals... and then sometimes the women changed their names again and the editables were stuck with the previous version. And for some reason, we were missing one really common "Mr. and Mrs." format for assigning to the Mrs....3 -
WOWWWW Keri Barnhart! THAT IS A LOT! But so has this process been, so I totally get it. I look forward to digging into this. Thank you SO MUCH for sharing regarding this intense project. It's very kind of you and I know it's because you understand how labor-intensive it is and want to help the next guy.
One response from my initial reading of all of this is that, YES, when it says the addressee/salutation exists in records, it WOULD BE NICE if it could list where! I don't understand why it wouldn't be possible if the process is being stopped by those records. Again, this would be something to take to a suggestions page or to the developers?1 -
Suzi Briscoe:
WOWWWW Keri Barnhart! THAT IS A LOT! But so has this process been, so I totally get it. I look forward to digging into this. Thank you SO MUCH for sharing regarding this intense project. It's very kind of you and I know it's because you understand how labor-intensive it is and want to help the next guy.
One response from my initial reading of all of this is that, YES, when it says the addressee/salutation exists in records, it WOULD BE NICE if it could list where! I don't understand why it wouldn't be possible if the process is being stopped by those records. Again, this would be something to take to a suggestions page or to the developers?I have never been accused of writing too little. ? But add/sal cleanup is a huge project with a lot of moving parts that you have to work out! My tips and guides for it are much easier to read when I have a full powerpoint set-up available and can use visual aids.
Maybe one day, if I ever have the time, I'll put together a more complete presentation guide with handy boxes and arrows and color coding. (I used to do training for my team, so I know how useful a good picture with color-coded labels can be when explaining database structure and clean-up!) Until then, if you need someone who has spent hundreds of hours with Addressee/Salutation clean-up and has a lot of advice from experience, I am happy to share what I know to hopefully prevent headaches.
2 -
Keri Barnhart Sounds like a great bbcon topic to me!!!4
-
Linda Burns:
I don't see a problem with the solution you're posing. If you have a link to a sugestion that I can vote for it, I'll gladly do so.Linda Burns I just shared some thoughts in Ideas for Raiser's Edge (RE7-I-5897) if you or anyone else would like to comment or vote on it!
0 -
@Suzi Briscoe A big reason that very few people should be able to create tables.
2 -
@Suzi Briscoe
Agreed - relationships always hide these things. And Editables - zug. When I have done clean up I have reviewed every editable to see if it can be made into a standard in the dropdown choices or if it does already exist but no one found it at the time. Goal being as few records with editable add/sals as possible. Oh! and the add/sals that is “under” the editable, those need to get changed to something standard in your menu.Helpful hint – I found that if I broke the Add/Sals into sections in the dropdown, others that might be looking could more easily find what they were looking for and now just wanna make a new one or click editable. So I made Add/Sals that are --Primary Addressee-- , --Primary Salutation--, etc. and then the appropriate format choices are in that section, so then you look in the dropdown and it's not as overwhelming to find what you are looking for
1 -
@Dariel Dixon - I was successful in querying non-constituents with the offending Add/Sal, but I have found no way to delete that Add/Sal type from non-constituents en masse. Is there a way? Global Change worked perfectly to delete it from the constituent records, but I still can't remove the value from my table b/c it still exists on tens of thousands of non-constituent spouses. Any suggestions? ? Many thanks!
0 -
@Amelia Ketzle: I wish I had words of encouragement here, but unfortunately I don't. I've always had to manually remove them from the non-constituents, and from there delete them. There may be a way to do so through the API, but I don't think the option exists through the regular UI. I imagine that you could use table cleanup to move them to another addressee, but that might not be helpful either.
@Dariel Dixon - I was successful in querying non-constituents with the offending Add/Sal, but I have found no way to delete that Add/Sal type from non-constituents en masse. Is there a way? Global Change worked perfectly to delete it from the constituent records, but I still can't remove the value from my table b/c it still exists on tens of thousands of non-constituent spouses. Any suggestions? ? Many thanks!
1 -
@Dariel Dixon
Thanks for your suggestions. Yes, I thought about Table Cleanup, but we don't have a suitable value to move them to, and really we want them gone (they're not adding value to our operations). Appreciate your ideas. I suppose there are worse problems to have.0
Categories
- All Categories
- Shannon parent
- shannon 2
- shannon 1
- 21 Advocacy DC Users Group
- 14 BBCRM PAG Discussions
- 89 High Education Program Advisory Group (HE PAG)
- 28 Luminate CRM DC Users Group
- 8 DC Luminate CRM Users Group
- Luminate PAG
- 5.9K Blackbaud Altru®
- 58 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 409 bbcon®
- 2.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- donorCentrics®
- 1.1K Blackbaud eTapestry®
- 2.8K Blackbaud Financial Edge NXT®
- 1.1K Blackbaud Grantmaking™
- 527 Education Management Solutions for Higher Education
- 1 JustGiving® from Blackbaud®
- 4.6K Education Management Solutions for K-12 Schools
- Blackbaud Luminate Online & Blackbaud TeamRaiser
- 16.4K Blackbaud Raiser's Edge NXT®
- 4.1K SKY Developer
- 547 ResearchPoint™
- 151 Blackbaud Tuition Management™
- 1 YourCause® from Blackbaud®
- 61 everydayhero
- 3 Campaign Ideas
- 58 General Discussion
- 115 Blackbaud ID
- 87 K-12 Blackbaud ID
- 6 Admin Console
- 949 Organizational Best Practices
- 353 The Tap (Just for Fun)
- 235 Blackbaud Community Feedback Forum
- 55 Admissions Event Management EAP
- 18 MobilePay Terminal + BBID Canada EAP
- 36 EAP for New Email Campaigns Experience in Blackbaud Luminate Online®
- 109 EAP for 360 Student Profile in Blackbaud Student Information System
- 41 EAP for Assessment Builder in Blackbaud Learning Management System™
- 9 Technical Preview for SKY API for Blackbaud CRM™ and Blackbaud Altru®
- 55 Community Advisory Group
- 46 Blackbaud Community Ideas
- 26 Blackbaud Community Challenges
- 7 Security Testing Forum
- 1.1K ARCHIVED FORUMS | Inactive and/or Completed EAPs
- 3 Blackbaud Staff Discussions
- 7.7K ARCHIVED FORUM CATEGORY [ID 304]
- 1 Blackbaud Partners Discussions
- 1 Blackbaud Giving Search™
- 35 EAP Student Assignment Details and Assignment Center
- 39 EAP Core - Roles and Tasks
- 59 Blackbaud Community All-Stars Discussions
- 20 Blackbaud Raiser's Edge NXT® Online Giving EAP
- Diocesan Blackbaud Raiser’s Edge NXT® User’s Group
- 2 Blackbaud Consultant’s Community
- 43 End of Term Grade Entry EAP
- 92 EAP for Query in Blackbaud Raiser's Edge NXT®
- 38 Standard Reports for Blackbaud Raiser's Edge NXT® EAP
- 12 Payments Assistant for Blackbaud Financial Edge NXT® EAP
- 6 Ask an All Star (Austen Brown)
- 8 Ask an All-Star Alex Wong (Blackbaud Raiser's Edge NXT®)
- 1 Ask an All-Star Alex Wong (Blackbaud Financial Edge NXT®)
- 6 Ask an All-Star (Christine Robertson)
- 21 Ask an Expert (Anthony Gallo)
- Blackbaud Francophone Group
- 22 Ask an Expert (David Springer)
- 4 Raiser's Edge NXT PowerUp Challenge #1 (Query)
- 6 Ask an All-Star Sunshine Reinken Watson and Carlene Johnson
- 4 Raiser's Edge NXT PowerUp Challenge: Events
- 14 Ask an All-Star (Elizabeth Johnson)
- 7 Ask an Expert (Stephen Churchill)
- 2025 ARCHIVED FORUM POSTS
- 322 ARCHIVED | Financial Edge® Tips and Tricks
- 164 ARCHIVED | Raiser's Edge® Blog
- 300 ARCHIVED | Raiser's Edge® Blog
- 441 ARCHIVED | Blackbaud Altru® Tips and Tricks
- 66 ARCHIVED | Blackbaud NetCommunity™ Blog
- 211 ARCHIVED | Blackbaud Target Analytics® Tips and Tricks
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- Luminate CRM DC Users Group
- 225 ARCHIVED | Blackbaud eTapestry® Tips and Tricks
- 1 Blackbaud eTapestry® Know How Blog
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)
- 1 Blackbaud K-12 Education Solutions™ Blog
- 280 ARCHIVED | Mixed Community Announcements
- 3 ARCHIVED | Blackbaud Corporations™ & Blackbaud Foundations™ Hosting Status
- 1 npEngage
- 24 ARCHIVED | K-12 Announcements
- 15 ARCHIVED | FIMS Host*Net Hosting Status
- 23 ARCHIVED | Blackbaud Outcomes & Online Applications (IGAM) Hosting Status
- 22 ARCHIVED | Blackbaud DonorCentral Hosting Status
- 14 ARCHIVED | Blackbaud Grantmaking™ UK Hosting Status
- 117 ARCHIVED | Blackbaud CRM™ and Blackbaud Internet Solutions™ Announcements
- 50 Blackbaud NetCommunity™ Blog
- 169 ARCHIVED | Blackbaud Grantmaking™ Tips and Tricks
- Advocacy DC Users Group
- 718 Community News
- Blackbaud Altru® Hosting Status
- 104 ARCHIVED | Member Spotlight
- 145 ARCHIVED | Hosting Blog
- 149 JustGiving® from Blackbaud® Blog
- 97 ARCHIVED | bbcon® Blogs
- 19 ARCHIVED | Blackbaud Luminate CRM™ Announcements
- 161 Luminate Advocacy News
- 187 Organizational Best Practices Blog
- 67 everydayhero Blog
- 52 Blackbaud SKY® Reporting Announcements
- 17 ARCHIVED | Blackbaud SKY® Reporting for K-12 Announcements
- 3 Luminate Online Product Advisory Group (LO PAG)
- 81 ARCHIVED | JustGiving® from Blackbaud® Tips and Tricks
- 1 ARCHIVED | K-12 Conference Blog
- Blackbaud Church Management™ Announcements
- ARCHIVED | Blackbaud Award Management™ and Blackbaud Stewardship Management™ Announcements
- 1 Blackbaud Peer-to-Peer Fundraising™, Powered by JustGiving® Blogs
- 39 Tips, Tricks, and Timesavers!
- 56 Blackbaud Church Management™ Resources
- 154 Blackbaud Church Management™ Announcements
- 1 ARCHIVED | Blackbaud Church Management™ Tips and Tricks
- 11 ARCHIVED | Blackbaud Higher Education Solutions™ Announcements
- 7 ARCHIVED | Blackbaud Guided Fundraising™ Blog
- 2 Blackbaud Fundraiser Performance Management™ Blog
- 9 Foundations Events and Content
- 14 ARCHIVED | Blog Posts
- 2 ARCHIVED | Blackbaud FIMS™ Announcement and Tips
- 59 Blackbaud Partner Announcements
- 10 ARCHIVED | Blackbaud Impact Edge™ EAP Blogs
- 1 Community Help Blogs
- Diocesan Blackbaud Raiser’s Edge NXT® Users' Group
- Blackbaud Consultant’s Community
- Blackbaud Francophone Group
- 1 BLOG ARCHIVE CATEGORY
- Blackbaud Community™ Discussions
- 8.3K Blackbaud Luminate Online® & Blackbaud TeamRaiser® Discussions
- 5.7K Jobs Board