Is there any kind of workaround in the works for this?

Wondering if this previous question has been addressed. Is there any kind of workaround in the works for this? An ability to export all NXT-only attachments, for instance? Any way to generate a query or list of attachments added only to NXT?

This seems very much a case of functionality being driven by what Blackbaud thinks is great, regardless of what USERS need and desire. While the functionality of attachments via NXT is easy, that ease comes at a cost for users who need to do anything more than simply view attachments. As in the comments below, we lose reporting abilities, we lose ability for our tagging/filing accurately, we lose actual data if there is a system issue with the database needing a restore. Until NXT has full functionality of database view (and it's not even close right now) it is very short-sighted of Blackbaud to make this decision. Listen to your users - we are the ones who are paying for this service and it must serve our needs. Don't get me wrong - I love a lot of the changes that NXT has brought in. But change must be driven by, and result in, improvement in functionality.

Can you advise the new modern approach 

If there is no plan to implement a way for Attachments to be view-able (and as a result, query-able data) in Old Database view, then please remove the Tags function. This function makes DOs think they are putting attachments into categories that we can then query from, and pull data lists on, which is not reality. The Tags table makes no sense since there is no way to pull a list on them.

Your "brand new approach" is great.
And easy to use.
And even fun to use.
BUT if we EVER had to do a system restore - it would all vanish.
So while you don't see the necessity to focus on supporting this issue, those of us who have worked in the system for years, and know that despite all the best intentions and precautions, a system restore is a possibility still see real value in address this issue.

Is there any kind of workaround in the works for this? An ability to export all NXT-only attachments, for instance? Or some kind of flag/notice in RE7 that will tell users that they need to go look at NXT for additional info?

Since it's been nearly 2 years since the original response and it's still a problem that many of us are encountering, it would be really helpful to have some way of approaching this other than 'well, deal.'

Agreed! NXT simply doesn't have the functionality to be used by all staff in our organisation (as I’m sure is the case in others), which means the database managers still use database view. If information is not readily available and transferable in both, it seriously reduces our trust in NXT.

I think it is time for Blackbaud to review and re-assess the possibilities and challenges associated with this issue which continues to raise questions and concerns.

Is it even possible to filter an action  list in NXT based on if there is an attachment?

Is this an output field for lists etc?  

Is the brand new document storage approach now also able to restore those documents if a factory reset of RE NXT is required or would all those documents still be lost along with user photos nxt invited users, etc.?

Disappointing answer. Having these NXT files not feed back to database view impedes our work and means double handling - it creates more work and problems than it solves. It also impacts the ability to merge constituents and adds considerable work. 

Please do NOT stop us from being able to add media in the database view unless you enable merging constituents in the webview at the same time!  Having the merge function in the database view and items in the webview that disappear when constituents are merged is the worst thing ever. How about an alert that is more specific to the records I'm merging, or a way to query what media has been added in the webview?  Please help us keep our databases clean! 

Please either disable attachments in web view or make them appear in database view. Otherwise it makes more confusion to users then benefits. 

This is also a problem when merging duplicate records. We now need to open the record in NXT to make sure we don't delete something that doesn't appear in the database view.

Sunshine, I added an Action Attribute and a Gift Attribute to indicate an NXT Attachment present on a record.  It's easy enough for Action, because you can add/edit the Attribute from NXT.  More difficult for Gifts, because you can't yet access the Attribute from NXT, but Gift Attachments are added in batches, so I just put together a query in 7, turn it into a list in NXT, attach all the files in NXT, and then Global Change to add the appropriate tag to the query in 7.  Not great, but better than the alternative of not being able to put Attachments on Gifts or Actions at all.

This is very disappointing. I get that you are driving people to use NXT over the database, but NXT does not offer enough functionality for database managers and other roles yet. It is doubling my work to have to check everywhere to see if media was added.

At least show a placeholder that media has been added for a constituent, action or gift record in NXT. I work mainly in the database and have no idea if something has further backup in NXT.

also disappointed.  we too have staff exclusively in RE7 and others exclusively in NXT and there are already too many things that you can only do in one or the other.  until you can have us all in NXT (data entry/ack!), don't separate the two in terms of this kind of functionality.

I am also disappointed with this answer.  Could we get more explanation as to how the new "document storage approach" will function?