SFDO-Community-Sprints/Membership-Essentials-App

NPSP Integration

Opened this issue · 3 comments

Build an adaptor package that provides additional functionality for orgs with NPSP

ACs

  • When a membership with a recurring renewal/payment schedule is created, utilize NPSP Recurring donations to create next transaction and related it to membership record
  • Allow recurring donation to identify the membership products to use for scheduled donations
  • Allow recurring donations created via transaction with Elevate to create a membership and the related records
  • Use of General accounting units for the products assigned to membership and used on recurring donations
  • use of or, replacement of, the NPSP customisable rollups for the existing membership fields (currently use opportunity record type membership)
  • allow NPSP data import wizard to handle creation of memberships (currently does this from opportunities with record type membership)

Further conversation from the Nov 2021 APAC sprint -
Using NPSP is highly recommended, specifically recurring donations and payments, but their functionality alone does not need an adaptor. For this sprint, we have added a checkbox to Opportunity that can be triggered as desired (flow, apex, etc), that should trigger membership related automation on that opportunity. That automation focuses on linking OLIs to existing memberships or creating new memberships if none exist. None of this requires NPSP.
This has focused the adaptor package to two specific areas:

  • A lookup to recurring donation on the membership
  • Automate product selection on when recurring donation creates opportunities, copying products from the membership related to that recurring donation
  • A lookup or integration between GAU (GAU Allocation?) to product
  • Decide who wins when both campaign and product have gau's assigned

Further from May 22 sprint

  • consider if the NPSP Settings for Memberships (under Donations section) will need to be reset so they don't cause a clash - or take advantage of them if they will be useful, e.g. Grace Period
  • further to NPSP import wizard, would automation for creating membership from opportunity cover new memberships first entered as an opportunity through Gift Entry batch?