FLOW: Create Membership Create Data Processing Event Listener #193
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Expiry Alert from Metecho Your Dev Org for "FLOW: Create Membership Create Data Processing Event Listener" on Membership Schema and Benefits Epic 2024 Sept Sprint is set to expire in 3 days on Oct. 27, 2024, 5:06 p.m.. You have uncommitted changes on your Org that will be deleted. If you do not want to lose these changes, please log into Metecho as user "jenncarneiro," navigate to the Task, and click the "Retrieve Changes from Dev Org" button. We appreciate your contribution to the Salesforce community. Thanks!
DebbieN-SF
reviewed
Nov 5, 2024
There was a problem hiding this comment.
Tested difference scenarios but couldn't get membership to create.
- Test 1 Data
Membership Type = Product Name
Duration e.g. 1 year
Sale price = might not need to match standard price
Product SKU = needed to match product
Organization name = needed as all opportunities are created for the account not the contact
Populated contact not recipient
Test results
Account is Imported, contact is created, opportunity is created
Created 3 accounts
Created 8 Contacts
Created 10 opportunities
Created 0 Memberships - Test 2 Data
Membership Type = Product Name
Duration e.g. 1 year
Sale price = might not need to match standard price
Product SKU = needed to match product
Organization name = needed as all opportunities are created for the account not the contact
Populated contact as well as recipient
Test results
Account is Imported, contact is created, opportunity is created
Created 2 accounts
Linked Contact as email was the same but name was different
Didn’t create recipient contact
Created 8 opportunities
Created 0 memberships - Test 3 Data
Manually created opportunity
Added membership product
Updated opportunity to closed won
Test results
Didn’t trigger creation of membership
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A few questions were outstanding at time of submit:
Is there a naming convention for Membership Name, as it is not autonumber. Currently I have Account Name - Product Name - Today’s date - No, not yet, this seems a good start
** ok left as is.
Is the Start Date today? I don’t see a date in the form submission. Is it related to Grace Period in any way? Start date should be created date on the MFS if it's new, otherwise don't touch.
** left as today.
Is the Status always ‘current’? Yes - different process handles expiration
** 'current' is set
Do we leave Type field blank? There is a picklist on membership (Individual, Organization, Household) and a free text field on the membership form submission. Also don’t seem to be able to determine the type from the account. I think we should probably add this...
** left as is for now as picklist is restricted. Can revisit logic?
Critical Changes
New Flow added to create membership
Changes
n/a
Issues Closed