Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit RENXT-I-7451 Add Export to NXT.
Bring exports over from database view
Merged
The query function in RE NXT works; however, many times we need more in depth, detailed information about the cohort captured in the query. It is imperative that we have the exports that we built in the database view to also be in the web view of RE.
-
Deanna
- Feb 20 2025
- Planned
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +222
Related ideas
Sample use of exports.
We create an event for all Board meetings and mark which members attended. We have an Event Type for every board meeting (ex. BOD Finance Committee Meeting).
I have an export that uses the Summary feature to return the number of each Event Type the Board member attended. I pull in the criteria separately for each type, so they are in their own dedicated column.
This summary feature is not available in Query or Lists and is a feature I use in nearly every export.
How is the EXPORT process in RE Database going to work when queries in 2026 can no longer be processed in RE Database, only NXT. Would it not be to our benefit to have the EXPORT process on NXT the same time the queries are only useable in NXT? To pull unique information from the Constituent/Gift databases we use a query for the EXPORT (not a query export).
Current Export in database view works very well - has many options on exporting data. Putting a large amount of reworking on clients in order to be able to maintain current functionality. Bring over the existing export with all of it's bells and whistles
If you are planning on discontinuing query in database view, please release a workable version of Export in web view by then too. Otherwise, it will just create friction in querying and exporting data if we need to create queries in web view and then go to database view to export it.
This is very important and required functionality!
And the ability to export in multiple formats other than CSV like FE Export allows (including the Blackbaud Report Writer Database MDB format).
we use multiple queries for different types of mailings, but have one universal Export to send that specific list to our printing company
Please merge to idea 7451
It also is very important to be able to select different export criteria without affecting duplication of rows. Many orgs I work with will have lifetime, last five year cumulative amounts, along with phone/constituency code and other metric - and Export from database view helps to ensure one row per constituent. Query cannot do that.