Membership-Essentials-App icon indicating copy to clipboard operation
Membership-Essentials-App copied to clipboard

Published 20 hours ago • verified publisher icon SFDO-Community-Sprints

Design an automation solution for Membership naming along the lines of NPSP Opportunity naming

Open davidmreed opened this issue 4 years ago • 3 comments

ACs:

  • Ability to specify any field from the Membership object, or any static value, or combination thereof to specify a Name field.
  • Use merge syntax that is as close to NPSP's Opportunity naming syntax as possible.
  • Build parsing and merging code (possibly copied from NPSP) to support this functionality in an Apex trigger.

davidmreed avatar Sep 23 '20 17:09 davidmreed

Current version appears to use Lastname and Type of Individual even when a different type is selected (e.g. Household).

DebbieN-SF avatar Jun 29 '21 13:06 DebbieN-SF

Merge with #58

tobiasaw34002 avatar Mar 07 '23 17:03 tobiasaw34002

Had a brainstorming during March '23 sprint about this (see https://salesforce-external.slack.com/archives/C03E9GU0F43/p1680199911862449).

I think we should go within the MVP with a naming, which we define depending on the type used. Later we can make it more flexible. Proposal from my site that the name is created in the following way Contact.LastName & Membership__c.Type__c

If we implement this, we have to remove the logic in the quick action Contact.New_Membership.quickAction-meta.xml Here we have created a predefined name field with the formula Contact.LastName & "- Individual Membership" => remove this predefinition.

By automating this we can close story https://github.com/SFDO-Community-Sprints/MembershipSchemaAndBenefits/issues/64

waidner avatar Apr 07 '23 19:04 waidner