Automation to add a Constituent Code
Hi, I set up an automation to add a constituent code (Major Donor) to records if certain criteria are met. It also sends an email to the relevant people who can review it.
In some cases, they decide to remove this code from the record (the criteria is correct but in this particular case, we don't want the code). Is there a way to prevent the flow from adding it again?
Answers
-
@Sarah Woodard How are you identifying the donors to start? List, Query, something else? Also will those excluded be excluded forever (ie. beyond the end of the year/fiscal year)? Have you thought about moving the approval process to before the addition of the code?
Just a couple questions that could help to inform some thoughts for you as I am sure there is a way to do this.1 -
There will need to be logic that can identify who to exclude. That can be in the form of a constituent attribute or constituent note.
I would use constituent note (create a new notepad type, such as Major Donor Exclusion), that way the reasoning can be recorded as well in case in the future other fundraiser question why the record shouldn't be included.
In your automation, you can use the Note list (single constituent) API endpoint and filter on if there exists a note type = the type you created, if yes, ignore.
If you want to get fancy and remove more manually workload, you can do one of these 2 things:
- create another automation that display an adaptive card for the fundraiser to provide a reason why the record needs to be excluded, this adaptive card can then add the notepad with all the correct data and remove the constituent code.
- create another automation that runs "regularly" (daily or every few hours), that checks for constituent with Major Donor constituent code and the Major Donor Exclusion consituent notepad to automatically remove it.
2 -
I'm so sorry, I swear I checked back here and didn't see any responses so I'm just seeing them now. But lucky me, this is still an issue, so thank you for the suggestions!
@Dan Snyder they would be excluded forever, but I don't have a criteria that would help us determine this from the outset (it's a case by case thing). So the Major Donor Exclusion idea from @Alex Wong might be perfect. Not sure I can get as fancy as #1, as I'm still a newbie!
1
Categories
- All Categories
- 6 Blackbaud Community Help
- 213 bbcon®
- 1.4K Blackbaud Altru®
- 403 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 1.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- 15 donorCentrics®
- 360 Blackbaud eTapestry®
- 2.6K Blackbaud Financial Edge NXT®
- 656 Blackbaud Grantmaking™
- 576 Blackbaud Education Management Solutions for Higher Education
- 3.2K Blackbaud Education Management Solutions for K-12 Schools
- 939 Blackbaud Luminate Online® and Blackbaud TeamRaiser®
- 84 JustGiving® from Blackbaud®
- 6.6K Blackbaud Raiser's Edge NXT®
- 3.7K SKY Developer
- 248 ResearchPoint™
- 119 Blackbaud Tuition Management™
- 165 Organizational Best Practices
- 241 Member Lounge (Just for Fun)
- 34 Blackbaud Community Challenges
- 34 PowerUp Challenges
- 3 (Open) PowerUp Challenge: Chat for Blackbaud AI
- 3 (Closed) PowerUp Challenge: Data Health
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Product Update Briefing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports+
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Email Marketing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Gift Management
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Event Management
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Home Page
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Query
- 793 Community News
- 2.9K Jobs Board
- 54 Blackbaud SKY® Reporting Announcements
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)


