Does anyone else use the batch Global Change function?

Catherine Burns

Just a heads up if you use this feature - we have been having difficulties with the appeal and package being committed incorrectly after globally changing the amount to $0 for our failed recurring credit card exception batches. 


We are on version 7.94 (non-hosted) and since upgrading in Feb15 whenever we use the batch tools Global Change function to change the amount of failed recurring credit cards to $0 before committing them to the recurring gifts, the amounts are changed and everything looks good in the batch, but when the batch is committed all the gifts have the appeal and package of the gift in the first line of the batch. In the batch they still look correct, but they are wrong when the gifts are created. If the amounts are manually changed to $0 there are no problems.


I discovered this error in May and it has been a lengthy process with support trying to fix this and it has now been passed to the programmers. 7.95 is not yet available to us and may not fix the problem. 


I would be surprised if we are the only organisation having this problem, but if you have the same appeal and package for all recurring gifts it wouldn’t matter or you may not have noticed.

Jen Claudy

I use Global Change in Batch for our payroll gifts.  However, they're all Recurring Gifts, and the Appeal is the same (different Package).  I also don't use GC for Amount, only Dates and the Mktg Src Cde fields.


As a workaround, if it's the Amount field that is causing the problem, could you try leaving the amounts and then do a GC on the Gift Records after they're committed to your database?  Either use the Batch Number to Query for those Gifts for the GC, or put a text string in the Reference Field, which can be deleted with another GC (or the same one, once you know this process works).