Blackbaud just announced removal of query from database view in February 2026 - WHAT? - "That means you’ll no longer be able to create, edit, or run queries – or access the Query homepage – in database view. While functions like global changes, imports, and exports will remain available in database view, the core Query experience is fully transitioning to web view. " How will users be able to continue to create or edit new exports, global adds/changes or Imports without a query in the interim???? Care to advise???
There should not be a set date for DBView to be OFF, instead, once BB thinks they have everything in Web View, customers need to still be able to use both for a testing period, I'd say a year giving everyone the chance to work through a full phase of their projects, events and mailings that occur in a year. The way features are rolling out one tiny piece at a time, it is impossible to commit to working in Web View for trials at this point. My preference would be that DB view remains for database admins... web view is much slower with tile layouts and endless scrolling.
We use query for so much more as in previous comments below. Global features, extensive Export/Imports etc. NXT query is still clunky and from an Admin Role is not always easy to use. I highly recommend BB DOES NOT turn the feature off in DBView at all, but maybe limit its use to Supervisors/Admin users only
I totally agree with what is being said. Why is database view going. NXT is so clunky. We are not a big global company but a small charity/hospice which uses database and is great for our needs. I do a lot of work through queries on database if this is stopped my work load would triple.
Still need this since we export nightly thru Que to get data into Reeher/Fundraising Platform.....
@Trit - does that mean there is a shift from previous procedure, such as removing tables from Database view? And is that a guarantee?
I hope we wait until we have the systems in place we need...
Wish they wouldn't retired database view at all - I hate NXT, everything is so much harder to do for admin work
In November we announced that we will not retire database view features until an official announcement of the retirement of database view.
Do not remove from web view at least until the export issue of duplicates is fixed, and all global functions are running correctly.
Query is not just used as a simple grouping tool to hand off data to Export, Reports, ect. No, Query is used frequently to filter records that need to be cleaned up and adjusted.
Within Query we are regularly opening records and accessing various places on these records to perform needed edits. Why? Because some edits just can’t be done with a Global change/add and creating an Import file is not always practical. As there are many fields which still cannot be adjusted in the Unified View, prematurely shutting off access to Query in database view will make performing needed tasks difficult and unnecessarily burdensome to the customers (us) of Blackbaud.
Customers will now need to have the query open in Unified view and then also have the Database view open to perform such needed tasks -- Unified View Query to filter and group the records on one screen, and Database view on the other screen so we can manually look up and open each record to perform the necessary tasks.
It's a pain to continually flip between the two view of RE while working on projects. It would be nice to have Export fully functional in webview before query is only available in webview so users don't have to keep switching between the views and translating the changes between field names (Fundraiser/Solicitor, Opportunity/Proposal, etc.).
Query in webview also cannot yet display inactive Funds, Campaigns, Appeals, which is VITAL for our historic searches.
February 2026 is not a realistic date. Until all fields and functionality in database view are in web view, and Blackbaud understands the reason for each and every one of them, you are not ready to discontinue database view. Expect to hear a lot about this from attendees at Bbcon in October 2025.
Having Export/Import & Global Changes are not the only reason to hold off on removing database view query. There are certain fields that are not in web view yet (like fund relationships). And there is no way to mass update funds for these even in database view. So the only way I have to update these records, as funds can and do change for scholarships, is to use query in database view and manually change the fund on hundreds of records one by one. Query in database view cannot go away until this "Unified View" is built out more fully AND completely.