This is a necessity for us!

According to the BBaud Constituent List help, "When you open or refresh a list based on a static query or query list, it automatically updates with any changes made in the database view." But this does not happen, the Webview Constituent list does not actually update. So you have to go back to the original static query, open it, run it, save it - then finally it will update in your Webview Constituent list - very frustrating.

I second Kari Cheng's comment, and all of the others, for that matter. It would be great to have this fully implemented prior to the transition to NXT from database view. Thank you.

We are working to send out a monthly email through NXT where the list of recipients would change each month according to certain criteria. To be able to use a dynamic query would be much better (and a time saver) instead of having to pull a static query each time.

Hoping to see this implemented soon, as we are being told we are fully transitioning from Database View to RENXT soon.

Having a dynamic query would help us immensely with the cumbersome email receipt process! We cannot fully implement NXT's e-receipt function w/out the segmentation options provided with query. Specifically, letter code. While static query is great, it is not feasible to pull a static query every week for 5 letter codes.

I find it very useful to schedule emails for event registration reminders and dynamic queries are important to make sure you aren't spamming people who have either already booked or have already declined. Without dynamic queries it is not possible to schedule effectively and this costs time. I hope you can resolve this soon.

I was hoping with query being added to NXT email would allow us to choose dynamic queries for emails in NXT. At the very least we should be allowed to use dynamic queries and translate them to a query list. We have dynamic queries we use for recurring emails. It would be annoying to have to refresh those each time we need to use them.

Now that queries are available in Web View, hopefully dynamic queries will be integrated into NXT soon.

I think this would be useful for emailing lists from query not having to be remade each time, BUT could be solved by just allowing emailing using queries directly. If this creates a more limited view that users can then sort through, I wonder if using securities makes more sense.

But allowing us more access to our data I always support, so upvoted

We need the option to run lists from both dynamic and static

We need this feature for several recurring processes we run on a regular basis. I don't want to have to reinvent something new.

We use this functionality multiple times a week in database view. We would need to completely reinvent the wheel if query lists with dynamic queries was removed.

how are we supposed to make a list of many complex criteria?

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!