We went live yesterday with new Gift Entry, and despite testing in sandbox, have some issues, mainly regarding the matched opportunities.
We have thousands of recurring donations and hundreds of online purchases to match up in gift entry.
When finding an opportunity to match up and processing batch, they do not appear to be using the Close Date and Stage in the default values of the batch header. I haven't tested amount yet.
Is there any detailed documentation on how this is expected to behave? When the defaults are or aren't used? If it is possible to define which ones should use the defaults regardless of the opportunity details?
I'm waiting for the partial sandbox to spin up before I can test more thoroughly - the old one was broken by the recent NPSP update pushed to sandboxes presumably regarding the new npsp data import fields for recurring donations (most of which I'd already manually created).
Hi @James Browne, Yes Richa was on the case so we found the missing permission that was needed - the Elevate status field on Payment object (for anyone with the same issue let me know if you can't see the case with the details).
Just working with Finance on the most efficient way to deal with the defaults not being used for matched items business - probably mass update from a list view as we'll make sure our custom batch number field is populated..
thanks for all your help.
