At the turn of the new year we have to update our Campaign (which we use for calendar year) for each and every automated recurring gift. Unlike when they were manual and you could run a query and a global change to update the default Campaign ID for each active gift, you now have to manually select each gift, click on Amend gift amount and change the campaign ID within each record. This is incredibly time consuming and should be an easy batch adjustment. The automated gifts are quite the time-saver except for this transition.
I'm a bit late to this discussion, but I also agree with this issue. YMCA sets recurring payments up as part of the acquisition campaign, but if the gift goes on for more than a year, we want to change this to the recurring campaign for reporting.
We use the global update to make these changes, but most of the payment plans need to have amendments made to them during the set up process, and so the global update fails. This leads to manual updates of all of the affected records, which can lead to keying errors. If we could make this change without needing to use SQL, that would be a huge benefit.
We also need to update campaign each January 1. Currently our recurring gifts fall into 3 buckets:
Ones that I can run a regular gift import and it will update the campaign.
Ones that I can run an amendment gift import and it will update the campaign.
Ones that won’t process in either manner (due to an error that indicates “the starting on date cannot be less than the amendment date”) and I therefore have to do a one by one amendment on each gift in webview just to change the campaign. I have to do these manual updates every year on these same recurring gifts.
Please consider overriding this error when you create a functionality to global update/import a change to recurring gifts (amended or not). Obviously the error can be sidestepped by a manual amendment, so the capability exists to sidestep it with a global change/amendment/etc.
I agree. All of our gifts, including recurring gifts, include the Appeal, which is name according to the new Fiscal Year (25/26...). In the new FY the appeals need to be updated. Currently, we have to manually update each records via Amendment. We should be able to globally amend these appeals in the unapproved batch screen.