Ability to delete "Assigned Fundraiser"

The "Assigned Fundraiser" field RE NXT is also the "Solicitor" field in Raiser's Edge.  The assignment can be delete in Raiser's Edge but not in RE NXT.  Even when the relationship is ended in RE NXT, the name of the previously assigned fundraiser still appears in the top ID section of a constituent page.  Please provide delete ability.

  • Leah Payne
  • May 3 2019
  • Planned
  • Attach files
  • Emily Marshall commented
    03 Sep 20:03

    Super! Thanks for changing this to Planned :)

  • Emily Marshall commented
    03 Sep 19:49

    Not sure why this is not available in Web View as we are able to delete a fundraiser from a constituents record in database view. I don't understand why anyone would think having this as a permanent record is necessary.

  • Elaine Buescher commented
    27 Aug 14:54

    In the past, we have used this for raffle solicitors during our event fundraisers. It is irrelevant information now, and when it pops up, I delete those names. It would be very helpful to not need to go into DBV to do that.

  • Ursula Stacks commented
    26 Aug 16:01

    This is a MUST have! If we can do it in DB view, we absolutely need it in webview. This has to become the norm. We should not have to keep "requesting" the functionality we already have. It's maddening how these changes are removing abilities to do our jobs as well and efficiently as we used to.

  • Jennfier Helton commented
    26 Aug 14:49

    I completely agree this is necessary for data cleanup. I occasionally update fundraiser assignments in Raiser's Edge, only for the decision to be reversed a few days later, making the data obsolete.

  • Jaclyn Whitelock commented
    26 Aug 14:44

    With no "delete" option, it seems Blackbaud is assuming that a fundraiser could never be added in error, and records never merged. Both of these things happen, even at orgs where end dating rather than deleting is the overall practice. Mistakes happen, the ability to delete needs to exist!

  • Maya Rosman commented
    26 Aug 14:33

    This is a critical data integrity need. Sometimes Fundraisers are assigned accidentally and need to be removed. Sometimes you merge records and now they're listed twice. In webview, it seems that Blackbaud has defined what a Fundraiser is and how we should use those records much more narrowly than how the majority of users conceptualize it. This is yet another example of this. Allow us the ability to clean our records as we see fit that works best for our business practices. Don't impose these kinds of limitations where none existed before.

  • Laura Furtado commented
    26 Aug 14:25

    This is 100% needed. Right now I go to DBV if I need to delete a fundraiser that was inadvertently added to a record. There is no way to do that in NXT. We need this to keep our data clean if the addition was a mistake.

  • Susan Walters commented
    26 Aug 14:18

    This is necessary! Again, BB is disregarding the needs of db administrators.


  • Lori Kroening commented
    26 Aug 14:11

    I had no idea that the ability to delete fundraisers doesn't exist in NXT. I can't imagine why not. It's easy enough for records to get cluttered without being required to preserve a history of assigned solicitors. That's what actions are for. If the fundraiser didn't record any actions, we don't need to know that at one time they were assigned to this person--and they apparently weren't doing their job.

  • Carlene Johnson ⭐ Community All-Star commented
    26 Aug 13:41

    I need Blackbaud to stop assuming they know what is "best practice" for organizations. While I can appreciate that it is a better idea to end a relationship rather than delete it, BB has left us without the ability to clean up our own data.

    Whether it is the result of an inadvertant error or from merging records, we need the ability to clean up and maintain our record in the way that we deterimine is best.

  • Teresa Fox commented
    22 Apr 20:10

    Yes, please provide delete ability in NXT.

  • Rachel Cavalier commented
    14 Apr 13:19

    Along with the reasons mentioned by other in these comments - we've merged another organisations database into our own and they used assigned fundraiser in a very different way so it's necessary to be able to delete to truly unify the database.

  • JoAnn Strommen commented
    13 Apr 16:25

    Need abiltiy to delete solicitor/fundraiser assignments to maintain relationships and use RE as it was intended.

  • Kate Sklodowska commented
    10 Apr 18:44

    It is important to be able to delete a solicitor relationship rather than end-dating it. The use case is this: at the start of the fiscal year, when we are reviewing assignments, we sometimes add relationships provisionally. After a few days of evaluation, we may decide to change an assignment — meaning the relationship was never truly active. It was created in error and should be removed entirely, not closed with an end date.

  • Rachel Kulsdom commented
    10 Apr 13:49

    We always delete past canvassers/assigned fundraisers because of the duplication it can cause in Queries, and also if you are searching for records with no assigned canvassers

  • Devan Bessinger commented
    09 Apr 16:56

    Yes, this is crucial. Our organization does not keep staff members listed as a fundraiser who are no longer employed by our org. Their action records sufficiently reflect who the client worked with. We wish to only keep the current fundraiser assigned.

  • Sunshine Reinken Watson ⭐Community All-Star commented
    08 Apr 16:47

    This is especially important when mistakes happen. We don't need to see a fundraiser that was assigned in error in the fundraiser history of a constituent.

    Note that fundraisers with end dates no longer appear in the header of the constituent (unless the end date is today).

  • Lenny Zimmermann commented
    07 Apr 17:57

    YES. Not being able to delete solicitors has really complicated exported data. Oftentimes the query will display a former solicitor that has an end date. I have to constantly toggle between database and NXT when updating solicitors

  • Tatyana Leifman commented
    07 Apr 17:47
  • Load older comments
  • +59