EXPORT Module

June Ehrenberg

We use the Export Module in RE Database view everyday. When will this be available in web view?

Joe Moretti

Who knows at this point. It should be.

Lee Grisham

It seems they may not be:

https://community.blackbaud.com/discussion/84415/introducing-single-row-query-in-blackbaud-raiser-s-edge-nxt-a-smarter-way-to-export-your-data

Still doesn't really easily solve the problem with mailings if that is a thing that your org does, ours does. I don't think any options in NXT help with communicating with donors. Just putting Salutations into a merge field for their emails last week, it doesn't seem like it has been prioritized for this system.

Sunshine Reinken Watson

Yes, they will release it in query as a single row query result export. So, basically query and export in one. According to the last Product Update Briefing, it is scheduled for the first half of this year.

Joe Moretti

And combining query with export totally messes up all the exports that people have set up for decades. I mean what happens to all those exports that we have all created and rely on. Sounds like a bad move. Having queries attached to an export is hardly complex and confusing as Blackbaud states. There was no problem with having them separate. In fact you would have a go to export that you can use for all kind of different queries, so now the future will be creating an export for every single query. Blackbaud really needs to rethink this if the future is going to be export built into query.

Dwayne Dipasquale

Will unified view allow us to export to access database like we can in database view so we can leverage our existing crystal reports? I doubt they will provide this same level of service.

Dan Snyder

While the initial release may not have the ability to bring your exports from database view over, my understanding is that it will be something that is done in subsequent updates. So, if the initial release does not work for a particular task, nothing will change for the time being. If you need to build a new export then I always give it a try and if it doesn't work, I know I can use the "old way" and give feedback why it does not work at the moment. Then, as releases are made you can give it a try if that release addresses what didn't work originally.

Something I think was really important that Blackbaud shared previously was about how they are building out webview. Not only are they building functionality within webview, but they also have to build the write back actions to database view. They could just build in webview and let customers sync back to database view, but they have heard from customers that turning off features in database view is not something they want (see code tables as an example) until the whole of database view is retired. Just my two cents, or five now that pennies are being retired.

Dan Snyder

https://community.blackbaud.com/discussion/comment/311219#Comment_311219

@David Springer do you have an answer to this?

Megan Tope

It will never be available - we're getting "single-row query" instead of Export.

I find this extremely concerning, because we don't ONLY use Export to flatten one-to-many relationships, and I'm starting to suspect that Blackbaud does not realize this.

The Export module doesn't just flatten the file; it also allows you to export more fields in certain cases than what Query by itself does.

For example, an Event Participant Query by itself does not allow you to export certain Constituent fields, like summary information, assigned solicitor, etc. However, if I run an Event Participant Query through an Event Participant Export, I CAN export those fields.

If all we're getting with single-row query is the ability to flatten one-to-many relationships, that will be an enormous loss of functionality as a result of the transition to Unified View.

Sunshine Reinken Watson

Users can reuse their set up for exporting with the "Select from query" option (currently in the options tab of web view queries under Record Processing).

David Springer

https://community.blackbaud.com/discussion/comment/311234#Comment_311234

Hi all! Our first goal is getting the file flattening element into Query, including the additional filtering and fields that Export provides (and are currently missing in Query).

As with Query today, we'll initially support XLSX and CSV. Then we'll be looking to improvements like migration of database view Exports to Query, Query/Export scheduling, web view-only fields, and any other feedback items that come up.

I'd encourage anyone who needs Access to vote in the Idea Bank: https://renxt.ideas.aha.io/ideas/RENXT-I-8391

If folks need other formats, I'd encourage you to keep each format in its own idea. Each one would need separate development, so we want to make sure we're prioritizing those that people need the most.

Dan Snyder

Thanks @David Springer!