NXT lists is not an adequate replacement for Query Lists. The functionality is more limited, is not as responsive, and does not retain a change log. Additionally, it is in a completely different section of RENXT which makes workflow and tracking much more difficult.

Please bring Query Lists to web view. This is vital functionality. Thank you.

Please put query lists in webview. It is imperative for us to have this for combining multiple complex queries

I was told lists in web view would replace query lists, but it doesn't function the same. I have to make a list of every query I want to use and so I can pull in multiple queries. That is ridiculously time consuming.

Also I have been running the same queries in web view and in database view and the lag time is up to three times longer to run and save in web view. Are the developers working on fixing that, because this is a huge time suck when preparing solicitation segment queries

Please keep query lists and the change log feature! We need the ability to build static lists and modify them with various criteria. Also, having the ability to review query changes year to year is invaluable!

Please keep Query lists

PLEASE KEEP LIST QUERY from Database View!!! It is the the most efficient and accurate tool for pulling complex data lists, such as Direct Mail Appeals, Event Invites, Solicitor Portfolios, etc. Lists in NXT and merging queries is not comparable. Our job performance depends upon it. KEEP QUERY LIST!! Thanks

Agreed, keep the Query Lists

Agree. Query lists are so useful and are used for combination lists so frequently. Not having it in NXT will force many database users to stay in the database view rather than working to convert their work habits over to NXT.

We use these for many of our NetCommunity emails.

Keep Query Lists, Please!!!!

Please keep Query Lists - we use them for ALL of our mailing and email lists, and we can't be the only ones!

Query Lists are a crucial tool -- without this function, I will be sticking to Database view for now as it is how I build most of my segmented lists. Please also carry over the change log feature! I use this every single time I build a query list, which is multiple times a week.

Please carry Query Lists over to web view, we use it a lot for segmentation and running complex lists. The normal 'merge' function is great but you can only do two queries at a time. As someone mentioned further down, frequency of use does not equate to it not being important.

Echoing that change log is critical. Also, we have several historical query lists that aren't currently appearing in webview. Very concerning that we would lose access to these queries if query lists go away.

I was told Lists in web view would replace query list, but I recently discovered that I have to make a List of each of my queries and then I can create a List to add and remove Lists of queries. What a waste of time. Can you get Lists to pull from queries, without me making individual lists?

I was so excited about Query going over to WebView --- without Query Lists, there's still no sense for me to move out of DBView

Query lists is the only feature I can use to create custom mailing list for VIP events. The query list log allows me to see year to year changes to these special lists. Complex queries do not get the granular groupings needed. Also, sharing our QL's allow officers a chance to review the lists with the details panel.

Echoing comments below and being able to query on consecutive years giving is important.

In today's town hall the sentiment that "frequency of use does not necessarily indicate importance" was shared, which I think is a great explanation for this particular feature. While I may only use query list a few times a month, when I do use it it is absolutely critical to my work.

Query lists are super valuable for more advanced users because they make it possible to build nuanced lists in situations too complex for merged queries. Probably the reason database view QLs have low usage numbers is the extremely limiting output options. I would strongly recommend an enhanced QL in NXT with more output options. ALTERNATIVELY if the "Start with a query" and Add/Exclude options in NXT Lists allowed us to select BOTH static and dynamic queries, NXT lists (whose output options are far better than QL's) would essentially replicate QLs.