please move query lists over to web views we use these a lot and love the change log feature. We need these to work in webview as database view eventually goes away.
@David Springer - so if you say Query Lists are redundant of Lists - will Lists eventually be able to pull directly into Mailings, Exports & Reports when those are built out? Or will the only option continue to be to reconvert the List back into a Query so that I can pull it into those functions? Am I missing something? This doesn't seem lean to me.
I am another user who uses query lists weekly and does not see the implementation in webview as being an equal replacement for how I use them. It is an integral part of my processes. So I continue to use dbv for this process.
@Tracy, the final outcome will look like the prototype I showed in the video. We don't plan to bring forward query lists as is, because they'd be largely redundant with lists and query. The only remaining piece we haven't implemented is the change log, which is planned for a bit later this year. We'll update this idea when that work is complete (and publish in What's new like usual).
@Rachel, that's true. I'll add that to the backlog, but in the meantime you can create an empty query to use as a starting point for lists (such as Constituent ID equals 0).
There are still bugs that need to be addressed. If you try adding a dynamic query to a brand-new empty list, it will pull in all constituents in your database in addition to those in your desired dynamic query. Until that is fixed, we still can't easily use it. See example below. I exported the file to confirm, and sure enough, it included 170k instead of the 515 we wanted.
@David Springer, so does that mean that Query List should be available in WV now? I've checked and don't see it under Query. I looked under the Constituent List area, and the enhancements described in the YouTube video you posted really don't fill the void. I don't want to have to reconvert the List to back to a Query if I need to pull it into a Mailing, which is only currently a possibly in DBV anyays. I'd still be curious if you have more details to answer @Amanda Mogridge's original question regarding full implementation timeline and how the outcome will look?
@Amanda Mogridge thanks for pointing that out! The town hall can be found here now. The only remaining piece we haven't completed is the change log, which is planned for later this year.
@David Springer - we use query list all the time to add and exclude queries based on a variety of criteria and the Change Log is extremely helpful. Can you provide an update on this planned idea implementation timeline and how the outcome will look? The link to the town hall below is broken and I wanted to remind myself where things left off and what's next. Thanks!
Why do we have to vote on tasks that are already available in database view? I really hope you listen to your long-time users and NOT get rid of database view in early 2027...or until EVERYTHING that is available in db view is also available in web view.
Please move full functionality of query list to web view. We create queries and add/exclude other queries to build mail/email lists on a daily basis! It is a critical function!
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.
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!
@David Springer - so if you say Query Lists are redundant of Lists - will Lists eventually be able to pull directly into Mailings, Exports & Reports when those are built out? Or will the only option continue to be to reconvert the List back into a Query so that I can pull it into those functions? Am I missing something? This doesn't seem lean to me.
I am another user who uses query lists weekly and does not see the implementation in webview as being an equal replacement for how I use them. It is an integral part of my processes. So I continue to use dbv for this process.
Unfortunately, webview lists won't have the flexibility of query list if we can't start from a dynamic query.
Yes, the change log feature is important!
@Tracy, the final outcome will look like the prototype I showed in the video. We don't plan to bring forward query lists as is, because they'd be largely redundant with lists and query. The only remaining piece we haven't implemented is the change log, which is planned for a bit later this year. We'll update this idea when that work is complete (and publish in What's new like usual).
@Rachel, that's true. I'll add that to the backlog, but in the meantime you can create an empty query to use as a starting point for lists (such as Constituent ID equals 0).
There are still bugs that need to be addressed. If you try adding a dynamic query to a brand-new empty list, it will pull in all constituents in your database in addition to those in your desired dynamic query. Until that is fixed, we still can't easily use it. See example below. I exported the file to confirm, and sure enough, it included 170k instead of the 515 we wanted.
@David Springer, so does that mean that Query List should be available in WV now? I've checked and don't see it under Query. I looked under the Constituent List area, and the enhancements described in the YouTube video you posted really don't fill the void. I don't want to have to reconvert the List to back to a Query if I need to pull it into a Mailing, which is only currently a possibly in DBV anyays. I'd still be curious if you have more details to answer @Amanda Mogridge's original question regarding full implementation timeline and how the outcome will look?
@Amanda Mogridge thanks for pointing that out! The town hall can be found here now. The only remaining piece we haven't completed is the change log, which is planned for later this year.
https://youtu.be/-Yz1caEXunc?si=XPhI8dK1ZYIda7Pz
@David Springer - we use query list all the time to add and exclude queries based on a variety of criteria and the Change Log is extremely helpful. Can you provide an update on this planned idea implementation timeline and how the outcome will look? The link to the town hall below is broken and I wanted to remind myself where things left off and what's next. Thanks!
Why do we have to vote on tasks that are already available in database view? I really hope you listen to your long-time users and NOT get rid of database view in early 2027...or until EVERYTHING that is available in db view is also available in web view.
Please move the full functionality of query list to web view.
Please move full functionality of query list to web view. We create queries and add/exclude other queries to build mail/email lists on a daily basis! It is a critical function!
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