We need the ability to send emails to constituents who are flagged "email only" for communications. In addition, we need to add a query filter to exclude constituents who have asked not to recieve our magazine. This is important in order for us to continue to navigate the changing privacy laws in the U.S. and worldwide.

If Blackbaud wants to ultimately remove the Database View from Raiser’s Edge, they will have to incorporate all DBA functions in NXT Web View including the most basic functions such as creating a list/query in NXT and having every field available for including/excluding just like database view. As a DBA I cannot see myself working in NXT anytime soon since the functionality doesn’t exist for me to complete my responsibilities within Raiser’s Edge. Let’s get this done “Dynamic query” would make the BB Community happy!

Not having this functionality prevents DBA's from supporting their colleagues with something that is basic and greatly needed. When our fundraisers can open a list and have it auto update, the DBA is not needed beyond the set up, saving valuable time needed for other requests and solving other issues. WHAT IS KEEPING BB FROM IMPLEMENTING THIS?!!!!!!!!!!!!!!!!!1

Since this question was opened in 2016 - It doesn't seem like these votes matter. but for what it's worth - yes! Dynamic query is basic and should have been there from the beginning.

What's the point of RE NXT lists? You can't even create a mailing list excluding do not mail. I can't then create a dynamic query from database view so that I can exclude it in Lists, as all queries are static. Very frustrating.

I'm setting up a new solution for my team and am building everything in database view, as I have 6+ years of intensive RE experience but everyone else on my team will be completely new. They will only use NXT. I want to create default lists for them built off dynamic queries so they can find and contact constituents. Why do I have to duplicate effort by building a list in NXT AND a dynamic query in the database to do the same task?

Why are NXT lists still static? From a business perspective it doesn't make sense. Most users should interact with the data via a web front end, not in the backend database!

We need to be able to create lists based on dynamic queries. It is ridiculous that we don't have this as an option yet. This should be an easy thing to implement give that static queries are already included. Please get this added for us. It will make things much more efficient!

It's crazy that this isn't an option yet. We are loading in static queries every week to send emails. Why is it so hard to create a dynamic query option?

I have been a Database Admin for over 10 years and every time I try to make a small switch to NXT for something, I hit a road block. I have tried to empower my Development Officers to pull their own email list for communications. I still cannot do this since lists are ONLY based on static queries and not dynamic! Please make this change before we make the change to a new CRM.

I can't believe this is still unresolved. THIS VOTE STARTED IN 2016. JUST MAKE IT AN OPTION ALREADY.

Very obvious need - our development officers operate in NXT and the database team primarily functions in the database. It's crucial for us to give them the tools they need in NXT (i.e. a dynamic query) to search for gifts/constituents themselves.

obvious need

This would be very helpful. Instead of having people make thousands of calls via API's to gather all the data that need and then do some kind of Houdini data manipulation. Developers could make dynamic queries and pull the dynamic query lists in one API pull and get all the information they need. This would make everyone's lives and systems more efficient.

I cannot understand why this feature is even being discussed. It is . Dynamic query is basic and should have been there from the beginning.

This is a VITAL thing for us to make NXT usable to our Senior Leadership. The lack of this option is one of the things that is making them consider other tools. PLEASE make this happen.

PLEASE implement this functionality.

Now that the acknowledgment process has to be completely overhaled, and we have to use lists, it's even more important to expand their abilities. Right now, NXT and list making are so limited, I don't know how anyone is expected to adjust. My biggest complaint here is that we're all being ushered away from database view toward NXT, but NXT doesn't give us access to all of our quarriable fields. Implementing dynamic queries for NXT lists would be one step towards making this transition easier.

Please implement using dynamic queries for NXT lists - this is even more important now we have to set up new systems for our TY letters...

Please please consider this. We just discovered this as well as we have been trying to push more self service options on our users to cut down on time for them to get data and the number of requests coming to our department. The fact that these cannot be dynamic is not good. Now we are going to have to tell our users they need to create new lists each time they want to pull say a constituent list from Web View.