Re database view has always allowed us to mark fundraisers (solicitors) as the fundraiser on their own gifts. I discovered recently that this causes an error in RE webview saying that a donor cannot be a fundraiser for their own gift. I do not understand why the developers have chosen to remove this functionality in webview. This has always been possible in database view.

We use this incredibly strategically in our system. This is how we track give/get goals for our Foundation Board and this has been our practice for over a decade. Our Board members are all marked as fundraisers in RE with a goal of $5000. They can reach this goal either by giving that much themselves (as the donor) or by bringing it in through connections. Marking them as the fundraiser on all gifts they bring in (their own and from others) allows us to accurately track their give/get and make use of the standard reports that track fundraiser performance and progress towards goal. It also simplifies our general reporting and makes it easy to see at a glance what giving was generated by our Board. It's an elegant use of the solution.

This feature in database view isn't a problem and it is incredibly useful in simplifying reporting and process. The decision to suddenly make this impossible in webview will cause my organization a ton on issues and I don't see any material gain from it. If the concern was that users were marking donors as solicitors in error, I assure you that this is not the case for us and I am sure we are not the only ones using fundraiser credits in this way. If that truly was the reasoning behind blocking us from marking donors as the fundraiser on their own gifts, I suggest adjusting this to a pop-up error message asking if we're sure that's what we want to do. That way, there'd be a check on the process, but users who do this purposefully can still continue with their process.

If this is not addressed before the move to the unified view, this will cause a huge problem with our entry practices and will make it even more difficult to retain reporting integrity and to pull historic reports - since this would mean suddenly changing entry practices that have been stable in the 15 or so years that our organization has been using RE.