I'm struggling to enable allocations at the payment level. I've enabled payment allocations in NPSP custom settings, but continue to receive this error when trying to log a new record:
npsp.TDTM_Allocation: execution of AfterInsert caused by: System.NullPointerException: Attempt to de-reference a null object (npsp)
I think it has something to do with the fact that I also had to enable Default Allocations, which I assume automatically connect the opportunity to the allocation and NOT the payment - but when I disable this, I receive a different error saying that a Default Allocation is required in order to save an allocation at the payment level. I'm at a loss and need to fix this asap. Has anyone experienced this issue?
Hi @Eileen Kapp @Quixo Consulting - Just jumping back in her to remind of what I said on this previously - Payment Allocations are not documented or supported in NPSP even though there's a back way to enable it, as you've found. It's not actively tested as new features or other changes happen. Proceed with caution.
