In a training org, I tested setting up a second record type on recurring donations for legacy gift opportunity to take advantage of the object linking donations to a sort of master record without giving users yet another feature to work with. It worked wonderfully. When I created it in our sandbox, however, I could not save without entering an amount > 0 and a day of the month. Neither of these are applicable to a legacy gift opportunity.
The difference I find between my training org and the sandbox is that the training org has not upgraded to enhanced recurring donations. Unfortunately, once upgraded, one cannot downgrade. Also, this sandbox has a great deal of other work accomplished in it, and creating a new sandbox without enhanced recurring donations but with all that work reconfigured (whether through change logs--if possible to use change logs between sandboxes-- or by hand) would be time prohibitive.
Does anyone know of a way to circumvent Enhanced Recurring Donations requirement for an amount and a day of the month? These are not required fields as far as the field settings show, so I think the requirement must be coming from a flow or other feature. I did not find the requirement in NSPS settings.
The field to set the installment period is not included in this page layout, and I did not find an option to set the default.
@Divs Chauhan: Thanks for taking the time to reply!
I found a default on the installment period picklist field and removed that, but the error on the day of month persists.
There is also a trigger on recurring donations, but it is managed by NPSP and seems to disallow admins from changing it. (Note below that I renamed the recurring donation object to multi-payment gift.)
I do not find any validation rules either at the field level or at the object level.
I started following these instructions for disabling managed triggers, but I think I may be missing some information for creating a flow action that disables a trigger. I see a recommendation there for Salesforce Toolkit, but I do not want to risk giving org access to a third party tool.
I am still working this issue at the time of responding. If you have any more pointers, I would appreciate them.
