Since implementing Classy for recurring donations, I receive multiple emails, usually overnight, with this cryptic error:
Errors:
----------
Error #1:
Error Type: Other
Error Date: 2024-03-22 09:09:19
Message: "bad value for restricted picklist field: Recurring Donation"
Context: RD
Stack Trace:
null
----------
Error #2:
Error Type: Other
Error Date: 2024-03-22 09:09:20
Message: "bad value for restricted picklist field: Recurring Donation"
Context: RD
Stack Trace:
null
There's always a list of them, sometimes just a few and sometimes 100 or more, all the same, except for the time. Since it's a SF error, Classy has been unhelpful. The recurring donation sync is opaque. I can see what fields are involved but not what values are being sent. I have asked them for more information but they have not been forthcoming. I'm still hopeful I'll get the sync details from them.
RD records are being created but they are not getting updated with each new payment. I don't know where to look next. Any ideas?
@Rachel Fain There's a field in NPSP on the Recurring Donation object called "Installment Period" - that's the only place that NPSP has that kind of value and if you don't already have "Quarterly" there you can add it.
Do you have any Recurring Donation to Opportunity mapping set up in NPSP?
