Use case:
Rollup to set membership start date at the Account level based on Account (Contact Soft Credit)-Type Rollups that include both 'Donor' and 'Gift Membership Recipient' using a Filter Group.
Expected behavior:
Opportunities will roll up to the Account of any related Opportunity Contact Roles if the Filter Group criteria is met.
Observed behavior:
If a Contact Role is marked 'Primary' (regardless of the Role) AND the gift is related to Household record type Account, gifts are excluded from the rollup calculation. If I uncheck 'primary' on the Donor role, it is then included; and if I check 'primary' on a Gift Membership Recipient role, it is then excluded. If related to an Organization RT Account, a 'primary' role does not appear to impact the rollup.
My guess is that this was an intentional way to ensure hard credits were not accidentally included in soft credit rollups, but it doesn't appear to be documented anywhere and prevents using a single rollup for the use case described above. Easy workaround = separate rollups for HC vs SC—fine—but system behavior is not aligned with the expected result.
Can anyone confirm whether this is intentional (but undocumented?) NPSP behavior, or if unintentional whether it might be evaluated for a 'fix' to align automation with how filter groups are specified?
Hi Duncan, I agree that is counterintuitive and seems to disagree with docs. It was bugging me ;p so I just tested it on HH and Org gifts and it acts as you state and not as I would expect either. Primary Contact lookup alone should control the hard credit on Individual gifts, unrelated to that Opp Contact Role (OCR) primary checkbox, when Customizable Rollups are enabled. That primary checkbox on OCRs, to my brain, only comes into play if you have that special 'Always rollup to Primary Contact' box checked (which isn't best practice) or are not using customizable rollups.
Things have changed a bit in how the team tracks issues, but I don't see it in older issue lists on github as a known feature/bug. It might be worth posting a support ticket to see if you can get a straight answer. I can also try my avenues to the team.
