nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Filtering lists for "no fundraiser"

Beth Dunning

I understand that the "unassigned" tab in the work center is designed to capture *only constituents not in a fundraiser portfolio*. Unfortunately, that tab cannot be saved as a list.

Within "lists", my choices are "for" a specific fundraiser (or multiple), but there is no option for "none" or "no fundraiser".

The pain point there is that I find myself unable to set up a work flow that will *exclude* constituents that are in a fundraiser portfolio. I know I can exclude a list (i.e. a list of assigned constituents), but it's my understanding that exclusion becomes static and does not update dynamically. That isn't an acceptable solution for a dynamic work flow.

Am I missing an obvious solution? Are there work-arounds you have found to this?

Find more posts tagged with

Comments

Dariel Dixon

I think you need to reverse the way you approach this problem Beth Dunning‍. I would create a list with all constituents with a fundraiser assigned, and use that list to exclude from everyone else. That should leave you with the constituents without a fundraiser assigned.

Beth Dunning

Dariel Dixon‍, I'm still pretty new at RENXT, and perhaps I'm mistaken, but I thought excluding list A (assigned constituents) from list B (all constituents) rendered list A static. So as constituents are added or removed from portfolios, list B would not dynamically update to reflect those changes. If all I needed was a one-time data extract, your recommendation would work beautifully. But for a work flow, I need list B to be fully dynamic. Am I wrong in my understanding of how excluding lists work in RENXT?

Dariel Dixon

Beth Dunning‍ I've never heard that. That may be the case for queries in DB view, but I'm not 100% sure that lists work exactly the same in NXT. But, we don't know unless we try. I don't think that using exclude renders a list static. I'm not certain either way however.

I guess that's one of the many differences between the old ways and the NXT. It's still worth a shot though.

Dan Snyder

Unfortunately Beth Dunning‍ is correct in her description of how the exclude process works in NXT. The work around I used for a similar situation (birthday messages to unassigned planned giving society members) was to use a Power Automate flow and have a condition to look for the presence of a fundraiser.

Faith Murray

Dan has an interesting workaround that I have not explored. Our approach is to also mark all assigned constituents with a Prospect/Portfolio attribute (custom field in NXT). You could use a Prospect Type also. It's easy then to pull a renewable list in NXT from any constituent lacking the "Portfolio" attribute. The secondary benefit of this is that it allows you greater flexibility in assignment designations: for example, if your constituent already has a "Major Gift" solicitor, but you want to qualify those still lacking a "Planned Gift" or "Board Member/Volunteer" solicitor type.

Beth Dunning

Thank you, Faith Murray‍ - this is very helpful. I don't like the extra work of tagging the constituents, but I can appreciate the added flexibility this gives. I still think Blackbaud needs to revise the filtering options in RENXT, but in the meantime, you've given me a workable solution.

Beth Dunning

Thank you, Dan Snyder‍. I appreciate your approach to handling this issue.