If you have ever stared at Raiser’s Edge NXT Web View and thought, “I know what I want, but I’m not sure how to ask for it,” you are not alone. Queries remain the backbone of reporting, segmentation, and day-to-day sanity. And while Blackbaud continues to expand web-based tools like Lists, queries are still very much part of the Web View experience today, with additional improvements expected down the road.
This guide, updated for 2026, answers the most common questions we hear about running queries in Web View. It’s based on real questions from real users and backed by step-by-step explanations straight from our Blackbaud Ninjas training sessions.
What is a query in Raiser’s Edge NXT Web View, and why does it still matter?
A query is how you ask Raiser’s Edge a structured question. Who are my donors in Nebraska? Who gave to this fund last year? Which constituents belong to a specific giving society?
In Web View, queries are still the primary tool for answering complex questions. Lists are designed for quick, surface-level views. Queries are where DBAs and power users go when precision matters.
If you need logic, conditions, summaries, or repeatable results, you need a query!!
Where do I find queries in Web View?
In Web View, queries live under Analysis → Query. This is one of the first navigation changes that trips people up.
Once you are there, filters matter more than you think. Category filters, query type filters, and format filters can all hide your queries if you are not careful. If your query seems to have vanished, check the filters before assuming something is broken.
Blackbaud Ninja tip: if your queries look missing, they are usually just filtered out.
What is the difference between dynamic and static queries?
This is one of the most important concepts to get right.
- A dynamic query updates every time you open it. If a new record meets the criteria, it appears automatically
- A static query is a snapshot in time. It only changes when you save and refresh it.
Use dynamic queries when you want living results, such as current donors or active members. Use static queries when you need consistency, like a fixed mailing list or the output of a merge.
If you are ever unsure, start dynamic. You can always convert your logic into a static query later in the options tab.
How do I create a new query in Web View?
- Query type, such as constituent or gift
- Dynamic or static
Web View remembers your last choice, which can be helpful or confusing depending on your mood. Double check before you begin.
From there, you build criteria using fields that may look familiar but sometimes have new names. Attributes are now called Custom Fields. Solicitors are now Fundraisers. Nothing disappeared. Some things just changed outfits.
This is where the Blackbaud Ninja cheat sheets and videos save time and frustration.
Can I paste a list of constituent IDs into a query?
Yes. And this is one of the most useful features in Web View.
Using the “one of” operator, you can paste up to 2,000 constituent IDs directly into a query. This is a major improvement over Database View limits.
This technique is perfect when you receive a spreadsheet from leadership that makes sense to everyone except your database.
Paste the IDs, combine them with other criteria using OR logic, and move on with your day.
How do merged queries work in Raiser’s Edge NXT?
Merged queries let you combine multiple queries into one result using logic like AND, OR, XOR, or SUBTRACT.
A common example is including donors who meet one set of criteria and excluding those who meet another. Rather than building a massive single query, you create smaller, clearer ones and merge them.
Merged queries must use the same query type. Constituent queries merge with constituent queries. Gift queries merge with gift queries.
The visual diagrams inside the merge tool are worth using. They make the logic easier to confirm before you run anything.
Why do my static query results sometimes look wrong?
Static queries in Web View behave a little differently than you might expect.
The results tab does not always refresh automatically when underlying criteria change. Until you save and rerun the query, the results may reflect older logic.
A common workaround is changing the sort order, saving, and then returning to results. This forces a rerun and updates the output.
The key takeaway is simple. With static queries, trust the saved version, not just what you see on the screen.
What should I always include in query output?
Always include a unique identifier.
Constituent ID is the gold standard. Even if you think you will never need it, future you will disagree.
Other helpful output fields include name, address details, assigned fundraiser, and summary fields such as total giving.
Web View makes it easier to reorder columns and rename headers, which is a small change that saves a lot of time.
How do summary fields work in Web View queries?
Summary fields calculate totals, counts, or averages based on gift data.
For example, you can output total gifts to a specific fund or total giving over a time period. You can also apply gift type filters, such as excluding payments.
One important limitation to remember is that funds, campaigns, and appeals are searchable by description only. Codes will not work, and inactive records may not appear.
Summary fields are powerful, but they reward patience.
Can I safely export directly from a query?
You can export directly from a query, and Web View makes it fast.
That said, caution is required. Queries are grouping tools, not reporting tools. If your output includes fields that repeat, such as constituent codes or multiple fundraisers, you may get duplicate rows.
For mailings and financial reporting, queries should feed exports rather than replace them.
Think of query export as convenient, not foolproof.
How do I share a query with someone else?
This is one of the quiet wins in Web View.
Every query has a shareable link. You can paste that link into email or Teams and send someone directly to the query without explaining folders or naming conventions.
This alone has saved countless messages that start with, “Click Analysis, then Query, then General, then scroll.” Enough said.
What is the best way to learn queries in Raiser’s Edge NXT?
The fastest way to build confidence is to watch real scenarios, not just documentation.
The Blackbaud Ninjas have created a full playlist focused specifically on running queries in Raiser’s Edge NXT Web View. These videos walk through live examples, common mistakes, and workarounds you’ll actually use.
If queries feel intimidating, start there. Pause, rewind, and try it alongside your own database.
Queries in Raiser’s Edge NXT Web View are not a step backward. They are evolving. Some things are faster. Some things take getting used to. A few things still deserve constructive complaints.
What hasn’t changed is this. If you understand queries, you understand your data. And that is still one of the most valuable skills in nonprofit fundraising.
When in doubt, let the Blackbaud Ninjas walk you through it. They’ve already made the mistakes so you do not have to.
You May Also Be Interested In
Available to Watch Now
The end is near, it's time to start thinking about life after database view.
Watch Now
