Keep EXPORT separate from QUERY
Please do NOT include the Export as part of the Query output. Most DBAs have created hundreds of Queries, yet typically only a handful of Exports. Exports are often quite complex and are most are designed to work with multiple queries with minimal adjustments. If we combine Export with the Query, we will essentially need to create a new Export for each Query, which will be incredibly time-consuming and will slow down production. I urge you to reconsider this approach!
-
sheila loveland
- Dec 1 2025
- Will not implement
Related ideas
Hi all! I wanted to share a recent blog post, which covers this concern as well as other information: https://community.blackbaud.com/discussion/84415/introducing-single-row-query-in-blackbaud-raiser-s-edge-nxt-a-smarter-way-to-export-your-data#latest
The relevant section is below:
Can I still use one export with multiple queries (or vice versa)?
Yes! Using “Select from” functionality, which exists on the Options tab of queries today, you can set the criteria on one query, then use a second query for output. With this approach, you can reference the same base query for multiple single-row queries as needed.
There's also an image of the “New query” modal, where you can select the result layout and “Select from” query.
We aim to have the benefits of combining the two features as part of one workflow while still enabling the very common practice of using many queries for the same export over time.
I'm marking this idea as "Will not implement" because we're accounting for the use case described above, but please continue to share feedback and concerns as they come up.
In the link above there are also a few ways to learn more and share feedback, like our upcoming webinar series: https://community.blackbaud.com/discussion/84362/blackbaud-raiser-s-edge-nxt-insidetrack-to-the-unified-view-monthly-series#latest
HERE HERE Sheila. None of this RE NXT makes any sense to me.