Thank you for this video! Super super helpful.
I suspect that the Payment Amount field may be a custom field in your org, and Opportunity Amount may be labeled in a slightly confusing way (or vice versa - or they may both be custom).
Behind the scenes, Gift Entry uses the NPSP Data Import object to store all the information about a gift. On the DI, there is one field called Amount that is dynamic based on whether you're updating a payment or an opportunity. (I know this can be either very confusing or very slick!)
When you choose to update a payment in Review Donations, that Donation field will automatically update with the Payment's amount (and when you update an opportunity, the Donation field will automatically update with the opportunity's amount). In your example, it will still be $100 because the payment has the same dollar value as the opportunity - but try this with another set of data where the payment amount isn't the opportunity amount, and you'll see what I mean. In the current example, you can update the Amount field on the gift entry row, and if you've selected Update Payment, it'll only update the amount of the payment, not the parent opp when it's processed (and will not run into issues with batch totals).
I think the next steps for you are to figure out the mappings for your Opportunity Amount and Payment Amount fields, and that should point you in the right direction. Hope that helps!
5 个回答
