I'm glad this has been added. Thanks developers! How is it working for everyone?

This really should be standard and something we do not need to request and vote on. The ASK operator prevents inefficiency and helps users actually streamline their work. Please prioritize features like these over AI additions.

Exactly - since there is no batch report generated when committing a web view batch I want to use a standard report. But having to tell my staff to go to query, edit the query to enter the batch number, then go to standard reports and run the report is a waste of time when the same report in database view prompts for the query name as is runs.

This is essential functionality. I build <ask> operator queries with clients regularly and they have to link to reports to be useful. Standard Reports in webview are not helpful if they don't work with these queries.

Coming back here to add that the lack of <ask> function is really making it hard for me to use NXT standard reports, as much as I'd like to. Not being able to easily use it as a built-in filter for gift batch number, class year, appeal code, or any number of specific fields we might build into the initial query means we'd have to spend more time building extra, repetitive queries and doesn't allow us to pull a daily gift & pledge report (with our current system) of multiple batches if we need to.

We've also been working to try to cull our many "historical" queries, of which there are MANY duplicates, and not being able to rely on query <ask> for these to then be usable in reports (and the eventual export module in NXT), means we're not able to do our templating work that we were planning to do to continue that cleanup and organization project within DBV/NXT. We were super excited to be able to use that function to make raiser's edge easier for all users, including our department as administrators.

I've just discovered that you can't use <ASK> in NXT like you can in Database View. This is unacceptable. I use ASK in my queries EVERY DAY. It is so important to use these in standard reports and exports. It makes it so much easier than building a different query every single time, and keeps CONSISTENCY as well. PLEASE bring this into the Webview capabilities!

{"children":[{"type":"paragraph","children":[{"text":"I love using the ask operator to cut out a step on reports and exports that are run for different gift dates, gift batch numbers, etc. It makes things fast and efficient. Now I will have to find the query, open it, change the criteria, save it, then run my report/export. I wonder if there is low usage because you don't need to create a lot of queries with this operator. A single query can work forever! "}]}]}

I use the ASK operator EVERY SINGLE DAY. So do many on my team. This is a MUST!!!

This is also critical for Export when it is made available in Webview. We use many <Ask> queries with exports. This makes it easy for end users to get what they need without knowing how to modify a query or having to have 12 different exports set up to accomodate a single criteria change, like class year for instance.

Seriously??? we should not be having to even ask for this. Come on.

This is vital to our daily reporting!

For added clarification and on James Belich's request, I'm sharing a link below to where I got confirmation as to WHY I was unable to use query <ask> in NXT Standard Reports. And just to confirm, query <ask> does have webview functionality within query (as it should!), but it's being able to use query <ask> within standard reports that is my primary concern here!

There are admittedly a few other functions I yearn for on this list, but query <ask> functionality was the most mission critical for me so I prioritized that idea here. Maybe I'll do some of the others as ideas later, or if others share them I'll certainly try to vote for them. There is a list of things that are "not currently planned for web view due to low usage" on one of the dropdowns here: https://webfiles-sc1.blackbaud.com/files/support/helpfiles/rex/content/bb-db-to-web-reports.html

Agreed - critical functionality! Chris, did you find a list somewhere of what Blackbaud does not plan to bring over to NXT?

Why remove a function that we use?

This functionality is critical

We also use queries the same way and absolutely need this functionality!

This is a vital operator. I have numerous reports and exports that depend on queries using this operator. Without it, I will be forced to add many dozens of additional queries exponentially increasing the number of queries in our database and risking of forgetting to run all relevant queries through a report. I also use this operator for queries used in posting process. Again, without it, the time it takes to post will increase and reconciliation with FE will be more complicated. This is devastating.