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; } } }

Constituent List - exclude/include

Amy Bridges

How are we excluding current fiscal year giving AND only including last fiscal year giving on constituent lists? Seeing how these are the basis of email lists there should be more logic capabilities. Right now I've built a list of LFY donors and then built another list of CFY donors and used that to exclude from the LFY donors but it doesn't auto update and just seems really cumbersome.

Find more posts tagged with

Comments

Karen Diener

@Amy Bridges:
How are we excluding current fiscal year giving AND only including last fiscal year giving on constituent lists? Seeing how these are the basis of email lists there should be more logic capabilities. Right now I've built a list of LFY donors and then built another list of CFY donors and used that to exclude from the LFY donors but it doesn't auto update and just seems really cumbersome.

I have not attempted this via a List, but Query handles it quite well. You'll need to use the Gift Summary functionality toward the bottom of a constituent query.

Criteria would be - in English and not in RE-speak - anyone who gave $1 or more during last fiscal year, and gave $0 during this fiscal year. You'll want to specify gift types to include and possibly soft credits, but that's the starting point.

As an aside - I like to give people prompts to get started but not do their work for them, which is why I am providing a general response. Hopefully this gets you going in the right direction.

Amy Bridges

@Karen Diener hi! Thanks for your response. I have used the summary fields in query to do this just fine yet then I would need to build it as a static list but none of those options make for a truly dynamic experience.

Appreciate your feedback and help! I think what I am looking for doesn't quite exist in RE without manual manipulation.

Dariel Dixon

I think you're right @Amy Bridges. Lists were not designed to have that level of logic. It does seem a bit like a misstep to limit email campaigns to lists and not allow it to use queries where that functionality already exists. It does seem intentional though. I'd suggest searching through the idea bank or creating a new idea and letting us know, as that does seem like an oversight that would be worth fixing.

Karen Diener

@Amy Bridges:
@Karen Diener hi! Thanks for your response. I have used the summary fields in query to do this just fine yet then I would need to build it as a static list but none of those options make for a truly dynamic experience.
Appreciate your feedback and help! I think what I am looking for doesn't quite exist in RE without manual manipulation.

Why would this be a static list? No reason the query would not be dynamic. Or is the end goal to use webview to review the data? You could review data in Query in webview too.

Dariel Dixon

@Karen Diener, she can't use queries because she is using the email feature in NXT. The email only allows you to create an audience from a list, not a query. @Amy Bridges can only create a list from a static query. Maybe when the Constant Contact functionality comes along this will change.

Amy Bridges

@Karen Diener We send segmented emails by donor giving history. To send an email, you have to use a constituent lists, and to build a constituent list off a query, it has to be static. The need for the capability to create dynamic email lists that consider giving history logic seems like a given for advancement shops.

Amy Bridges

@Dariel Dixon will do, thanks for the reply! I do have an interest in Constant Contact integration - I am nervous about the investment piece though. NXT is already a huge investment for our university so the additional costs are daunting.

Karen Diener

@Dariel Dixon:
@Karen Diener, she can't use queries because she is using the email feature in NXT. The email only allows you to create an audience from a list, not a query. @Amy Bridges can only create a list from a static query. Maybe when the Constant Contact functionality comes along this will change.

Ah yup - I see that now. I kind of thought that might be the case but I was so focused on Query vs. List that I missed the end result that Amy stated. I really dislike that step of sending emails - write a query but then convert it to a list.

Definitely hoping that Constant Contact integration is better, but I've worked with Blackbaud products long enough to know better.

Faith Murray

@Dariel Dixon
I'm not sure it was intentional. Originally it seemed as though Lists was supposed to be the “better version of Query” in webview, completely redesigned from the ground up, just as webview batching was redesigned from the ground up. At a certain point BB realized that the old functions were much more robust than Lists and webview batching, and so they launched the plan to pull DB Query and Batch into webview instead - which is what they've been doing since last year. I think that is the reason that webview email links to Lists and not Query. My hope is that they add that connection down the road. But they have their hands full right now trying to meet their “complete webview functionality” by 2026 so as to deactivate DB view. So I don't imagine that other details like this will have much room in their priority list for awhile.

Dariel Dixon

@Faith Murray, I think I view this a bit differently. It seemed pretty clear when I first used NXT that lists were not a “better version of Query”, but a different grouping tool altogether. Lists for NXT only functionality, and query for general grouping. I do agree there is a bit of a mis-mash of styles and features…as they roll out new features, there haven't been updates to older modules to take advantage of the new functionality, and now we have this… It does seem like there are several loose ends where this type of thing happens. We do need to make sure that these things get closed.

Kisha Baker

@Dariel Dixon create a static query, put it on queue to refresh (daily/hourly/etc), use the query to create an NXT list. now its essentially a dynamic query/list.

Owen Norvell

@Kisha Baker:
@Dariel Dixon create a static query, put it on queue to refresh (daily/hourly/etc), use the query to create an NXT list. now its essentially a dynamic query/list.

Is there functionality to have a static query auto-refresh?

Dariel Dixon

@Owen Norvell No, there's not. There's just @Kisha Baker's workaround, which is pretty common…if you have access to queue.

Alex Wong

@Owen Norvell
This can be achieve via SKY API's Query API endpoint to refresh static query. Not very hard to implement if you have some experience with Power Automate and SKY API

Kisha Baker

@Owen Norvell yes, if you have the queue module.

Rebecca Tuszynski

@Kisha Baker are you in the US? I'm in Australia and I don't think we have access to the Queue module, what section is it located on the NXT menu bar?

Kisha Baker

@Rebecca Tuszynski I'm in the US. Queue is only in databaseview still. It's an additional module in Admin.