InsideTrack Scoop: Query and Reimagined Export Highlights

Tanya Fitzgerald · April 3

In January, we introduced a new monthly series designed to keep you closely connected to what’s ahead for Blackbaud Raiser’s Edge NXT®.  InsideTrack to the Unified View is designed to help you confidently plan and adapt your processes with clear, reliable updates straight from our product management team. 

Our third InsideTrack session in March focused on updates to Query and Export planned for release in Q3 of 2026 (July–September). While we couldn’t address every question during the live discussion, we’ve gathered the most common ones to keep you informed and ready.

Single row query and export functionality were key topics, and to get the most out of this recap, we recommend watching David Springer’s demo and reading his blog before diving in.

Key questions and answers: 

Single-Row vs. Multi-Row Queries

Can I control which record is displayed (e.g., primary, most recent, or a specific type)?

Yes. Many-to-one fields will generally offer more robust filtering capabilities than are currently available in export.

Can I sort one-to-many fields (e.g., display primary phone numbers first)?

Yes. A dedicated sort tab will allow for more flexibility than is available in export today.

Can I include the same field multiple times, into separate columns, with different filters?

The same field can be added multiple times into separate columns with distinct filters.

Can I switch a query between single-row and multi-row result layouts after it has been created?

No, the layout changes how it processes data, so must be chosen when the query is created. You will be able to use “Save as” to create a copy with the other layout, but any existing output fields will not be saved.

Will single-row queries behave exactly like database view exports?

No, single-row queries represent an enhanced approach, combining elements of web view queries with key filtering capabilities and commonly used fields from export.

Export Functionality

Will all database view export features be supported in web view?
Commonly used export features will be supported, including summary fields, many-to-one filters, address processing, and head-of-household rules.

Can I preview an export before downloading it?
Yes, you can preview an export before downloading.

Can I customize column header names and sizes and save those changes?
Header name changes can be saved. Column resizing is not currently saved, but an idea has been submitted in the Idea Bank.

Can I include multiple summary columns (e.g., last year, current year, lifetime giving)?
Yes.

Will exports in web view run faster than database view?
In general, timing is expected to improve. However, it may vary depending on the complexity of the query and dataset. When queries take time, asynchronous processing will allow you to keep working and be notified upon completion.

Will exports run in the background or be schedulable?
Exports will run in the background at launch, and scheduling functionality is planned shortly after the initial release.

Can exports be used in Power Automate or API workflows?
Yes.

Can I still export primary-only contact details (e.g., email, phone, address)?
Yes.

Will exports include attachments, proposal/opportunity data, or prospect insights?
These will not be included in the initial release but are planned for future updates.

Can export permissions be restricted?
Access can be restricted, giving users access to single-row result layout, multi-row result layout, or both. Ability to export queries will also be restrictable.

Migration of Existing Exports and Queries

Will existing database view exports migrate automatically?
All exports will migrate when the user initiates the migration process. Rebuilding will not be required.

Can I select specific exports to migrate?
Migration is currently an all-or-nothing process; however, you can bulk delete queries in each category after migration.

Can the migration tool be run more than once?
This is still being finalized but is expected to be supported.

Will folder and category structures be preserved?
Categories will migrate along with exports. If an export category has the same name as a query category, those exports will migrate into that existing query category. For this reason, some users may want to rename export or query categories.

Can I distinguish migrated exports from native queries?
You can filter by Result layout and once you've created single-row queries in web view, you can filter or sort by create date.

Is migration one way?
Yes. Migration is one way. Changes made in web view will not sync back to database view.

Will security permissions stay the same during migration?
No, single-row queries will have separate permissions in web view that can be set for users ahead of migration.

Can export templates be reused?
Exports will migrate with existing queries populated into their Select from field and remain linked during the transition. If needed, this “Select from” query can be changed later to export data from a different query.

What happens to database view exports after migration?
Exports will remain available in database view but they will not sync with web view.

Format and File Types

What file formats are supported for export?
CSV and XLS/XLSX formats are supported.

Is PDF export supported?
PDF export is not currently planned.

Is MBD format supported?
MBD is not currently supported but is under evaluation for future development. Please make sure to add your ideas to the Idea Bank.

Query-within-Query and “Select From Query” Functionality

Can queries reference other queries of different types (e.g., constituent, gift, opportunity)?
Single-row queries can select from other query types as Export does today.

Can queries be used within filters or summary fields?
“Select from query” functionality for gift-to-gift filtering is planned.

Can I create reusable template queries for output fields?
Using "Select from" functionality, you can reference the same base query for multiple single-row queries.

Can I clone or save queries with different layouts?
This is not currently planned; however, this can be achieved by using “Save As” or creating a new query based on the original one.

Can queries be merged while reusing export logic?
Yes. Merge functionality will work the same for both result layouts.

Fields, Criteria, and Additional Functionality

Will all fields be available across query types?
Our current priority is bringing export specific fields to query in web view, with additional fields planned for future updates.

Can I query on gift codes and constituent codes?
Yes, you can query on gift and constituent codes.

Can I filter by birthdate (day, month, year)?
Yes, this is consistent with current query and export functionality in database view.

Are soft credit recipient details available?
A soft credit gift flag is currently planned however enhancements are not currently planned. If there is more around this functionality that you would like to see, please vote in the Idea Bank.

Will proposal/opportunity fields be included?
Existing fields from Export will be in the initial release. Web-view only fields are planned for future updates.

Will prospect status fields and time-in-status be available?
Not in the initial release but planned for future updates.

Will system IDs and import IDs be available?
Yes, these are both planned.

Mail, Lists, Dashboards, and Additional Features

Will queries replace lists for email or mail usage?
Not in the initial release, however, the ability to consume query for email is planned for future updates.

Can queries be used directly in dashboards?
Dashboard integration is planned for future updates.

Will queries support segmentation for mail tools like Quick Letters?
Quick Letters functionality is planned and you will hear more about it in the Raiser’s Edge NXT Product Update Briefing.

Will dashboards refresh faster?
Dashboard speed performance is being evaluated separately from query and export.

Will queries be schedulable?
Scheduling a query is planned shortly after the initial release.

Will control reports support single-row queries?
Yes, control reports are being updated to work for single row queries.

Usability, Organization, and Governance

Why do queries and exports combine into one list?
Queries and exports will share the same list but can be filtered by Result layout. If current exports have the same name as queries, we'll append a differentiator to the name so it's clear. One option would be just adding (export) or (single-row) at the end if a query exists with the same name.

Are folders or subfolders supported?
Categories will be shared between query types, but subfolders are not currently planned. If you would like to see subfolders within categories, submit an idea in the Idea Bank.

Can I control permissions for single-row queries?
Single-row result layout will have its own permission in web view that can be set for users ahead of migration.

Will migration tools be restricted to administrators?
Yes, it will be restricted to administrators.

Can visibility be restricted by role or team?
Yes, this will have its own permission to hide from specific roles.

Upcoming InsideTrack Sessions

We hope you find the InsideTrack sessions valuable and are enjoying the chance to connect with our product management team.

Don’t forget to sign up for upcoming sessions as we move to the unified view.

April 14, 2026 @ 11 a.m. EST/4 p.m. BST
Import for Impact
May 5-7, 2026
Raiser’s Edge NXT Product Update Briefing
June 9, 2026 @ 11 a.m. EST/4 p.m. BST
Next Level Gift Management

Karen Diener · April 6

There is some good stuff here!

I did add this idea about the ability to include more details on soft credit recipients
https://renxt.ideas.aha.io/ideas/RENXT-I-9746

Please provide more detail about which export features will NOT be supported. See the below Q&A for reference:

Will all database view export features be supported in web view?
Commonly used export features will be supported, including summary fields, many-to-one filters, address processing, and head-of-household rules.

I'm not sure I understand the difference between the question and answer. Isn't "Save As" the same as "saving a query with a different layout? I may just not be reading it carefully enough:

Can I clone or save queries with different layouts?
This is not currently planned; however, this can be achieved by using “Save As” or creating a new query based on the original one.

A lot of good news in the "Mail, Lists, Dashboards, and Additional Features" section!

I'm looking forward to reading everyone else's feedback!