Looks like the current plan is to modify constituent lists to better reflect Query List in database view? So now we would have to go to Constituent Lists create a list there then go to Query to finish creating what is needed there? Please just move this functionality to Query in webview! Like most organizations, we use Query List every day for almost every query created. Why not have it in query in webview?

Currently in NXT, multiple constituent lists can be merged, but the same is not true for (static) constituent queries. We need to be able to merge multiple queries in NXT.

Export needs to move along with Query my office cannot function without export we build some pretty detailed queries and pull a lot of the data into the export. I viewed the queries and not even half of my queries have moved to NXT?

Would it be possible to shift Query Lists to Query function too? The current filters in Lists are very limited so we won't be able to use it to create the segments we need.

Although it is possible to create static lists in Query, push it into Lists and use the Query List function there, there is then no way to bring that back to Query. In any case, those options require more steps than what is currently available in database view.

Therefore, bringing Query Lists into the List function doesn't really replace the existing database functionality for us unless you can address those issues.

Please record the Town Hall on 6th August and make it available afterwards to registrants. We are in Australia and the Town Hall is the middle of the night for us. Thanks.

Can it be recorded please for those who can't attend?

Will there be query folders too?

Thank you all for the feedback! As you've likely noticed, we're now planning to better replicate Query List functionality in web view. In this case our implementation will be through enhancements to constituent Lists. If you'd like to learn more and see a prototype of our plans, please join me for a town hall on the 6th.

I look forward to showing what we have in store, answering questions, and hearing your feedback!

https://community.blackbaud.com/events/item/3/4499

comment CONTINUED...

Then we pull the query list of all constituents who opened an email into RENXT and apply a filter for constituent code = alumni and that RENXT list is used in one configuration then we pull the same list into RENXT without a filter to use for our Major Donor Prospect score configuration.

The issue with RENXT lists is that when I add new constituents to it, it overrides the filter and would require that I create a new list each month and update my configurations with the new list.

I have been trying to find a way to recreate the business process we have in place using RENXT lists and it has been unsuccessful. The business process requires that we end up with an RENXT list but when I add new records to the RENXT list, the filter does not reapply. I understand this is intentional function of RENXT lists (for good reason) but in my use case I need the list to update and reapply the filter. Details:

We track email opens as part of our engagement score metrics for Alumni and Major Gift prospects. Each month our team creates a list from the sent email opens and adds this list the the QUERY LIST

Query lists are essential to our weekly datasets! The process of adding/removing is so clean across various parameters that cannot be done in a single query. Love the view of the change log for auditing! Please transfer this over to WebView!

I was so excited to see that Query Lists is now planned! Thank you, Blackbaud!

I don't understand how you can say Unified View will be better when you don't currently include query list. Be better BlackBaud.

I utilize query list SO much!!! Please don't eliminate this from WebView

We utilize query lists to build upsert lists for our emailed newsletters. Having to create a list of all those to remove from the emailed list is critical for us and includes tens of thousands of emails. Query lists are much easier than building a query to do this.

We use query lists weekly to identify members our giving societies. Our societies have tiers based on class year, giving level, and constituent code. They cannot be built as a single query. With query lists, we can build each tier, and then we use query lists to combine them and remove all current members. It's so clean and accurate. We have 9 lists that are combined each time. Doing this through merge queries will be a nightmare and I can't image a scenario where mistakes do not happen.

I use Query Lists all the time for unduplicated mailing and email lists that include and exclude multiple various queries. I appreciate the ability to View the change log so I can see exactly how many records were added or removed. It also helps year to year to see what queries were included or excluded for similar mailing/email lists in the past. Please make this available in Webview/Unified View!

Please keep query lists. I use them frequently when I need to create invite lists for big events that require multiple complex queries that are difficult or impossible to combine into 1 query. i.e. alumni by major, alumni that give to

particular funds, alumni within a certain giving level, alumni with various activities, past attendees to events etc. These are all used by me to create certain event invite lists

Please keep query lists! We use them for so many things and the change log feature is so helpful. Being able to add or remove individuals is extremely important. Please keep these features!

I use query lists for the bulk of my queries. These must work in webview before database view goes away. It's so important.