Allow Philanthropic Interest to be edited on a constituent record in NXT
All other areas viewable in the Prospect management tab are able to be edited, except this one, which you have to go through the process of opening database view for. It annoys.
I 100% agree with my peers that this is a NEED for Unified View. My organization is wanting to grow our philanthropic revenue, and understanding a donor's interests is so important. Also being able to query on this would be incredibly helpful. Right now, we have to rely on attributes/custom fields, which makes no sense that we had to come up with an alternative solution when philanthropic interests exist in Raiser's Edge.
Currently, the "Philanthropic Interest" field, displayed as "Giving Preferences" in RE NXT is view-only in Webview. This limits frontline fundraisers and other users from updating donor preferences directly during interactions.
We’d like to request that this field be made editable in RE NXT Webview, similar to how it’s managed in Database View. This would streamline data entry, improve accuracy, and allow teams to capture donor interests in real time, enhancing personalization and segmentation for fundraising efforts.
Agree with comments below -- we want to encourage users to use web view, yet the philanthropic interest & contributions (aka gifts to other organizations) needs to be entered in database view because it is read only in web view.
With the shift to Unified View, this should also include the ability to edit Gifts to Other Organizations ("Contributions" in Web View) in the Prospect Management tile. This cannot be edited in Web View at all, and some data in Database View does not display in Web View (i.e. Comments for these entries). With the pending shift to a Unified View, this needs to be updated to be consistent with database view. Prospect managers and researchers use this to document external gifts in the public domain which can inform solicitation strategy. See https://renxt.ideas.aha.io/ideas/RENXT-I-895
We are having to physically delete ALL of our philanthropic interests and move them instead to attributes (aka, custom fields) so that our gift officers can make use of this VERY vital field. Please let us know what the plan is for this field going forward.
Adding my vote here and a comment to hopefully bump this up. Really want to see ability to add giving interests (and 'will not fund') through NXT. Same goes for contributions to other charities. These are often discovered through a MGOs initial research or during conversation with donors. It's not functional to only be able to add interests and contributions through database view.
Any updates on this? Seems so easy to just quickly configure this on the back end code to enable entry and update of this through NXT in a fundraising CRM!
NXT is supposed to be the view for major gift officers and therefore should have all the functionality related to major gifts. Leaving functionality behind in the database view is a contradiction and a hardship on smaller shops with a limited number of staff working in the database view.
I 100% agree with my peers that this is a NEED for Unified View. My organization is wanting to grow our philanthropic revenue, and understanding a donor's interests is so important. Also being able to query on this would be incredibly helpful. Right now, we have to rely on attributes/custom fields, which makes no sense that we had to come up with an alternative solution when philanthropic interests exist in Raiser's Edge.
We need this yesterday!
Currently, the "Philanthropic Interest" field, displayed as "Giving Preferences" in RE NXT is view-only in Webview. This limits frontline fundraisers and other users from updating donor preferences directly during interactions.
We’d like to request that this field be made editable in RE NXT Webview, similar to how it’s managed in Database View. This would streamline data entry, improve accuracy, and allow teams to capture donor interests in real time, enhancing personalization and segmentation for fundraising efforts.
Agree with comments below -- we want to encourage users to use web view, yet the philanthropic interest & contributions (aka gifts to other organizations) needs to be entered in database view because it is read only in web view.
I strongly recommend to allow edits to this area in NXT. It makes sense.
This is important for the functionality of this tile in web view.
New to NXT and am figuring out what is NOT available and this is one function that needs to be available through NXT.
With the shift to Unified View, this should also include the ability to edit Gifts to Other Organizations ("Contributions" in Web View) in the Prospect Management tile. This cannot be edited in Web View at all, and some data in Database View does not display in Web View (i.e. Comments for these entries). With the pending shift to a Unified View, this needs to be updated to be consistent with database view. Prospect managers and researchers use this to document external gifts in the public domain which can inform solicitation strategy. See https://renxt.ideas.aha.io/ideas/RENXT-I-895
We are having to physically delete ALL of our philanthropic interests and move them instead to attributes (aka, custom fields) so that our gift officers can make use of this VERY vital field. Please let us know what the plan is for this field going forward.
Please merge this idea with
RENXT-I-4200
Adding my vote here and a comment to hopefully bump this up. Really want to see ability to add giving interests (and 'will not fund') through NXT. Same goes for contributions to other charities. These are often discovered through a MGOs initial research or during conversation with donors. It's not functional to only be able to add interests and contributions through database view.
So important for us MGOs.
The fewer barriers between RE NXT and database view for MGOs the better.
Any updates on this? Seems so easy to just quickly configure this on the back end code to enable entry and update of this through NXT in a fundraising CRM!
NXT is supposed to be the view for major gift officers and therefore should have all the functionality related to major gifts. Leaving functionality behind in the database view is a contradiction and a hardship on smaller shops with a limited number of staff working in the database view.
I am reverting back to using constituent attributes (custom fields) because this isn't available.