Open Source Community Sprint project focused on building a schema for memberships, renewals, payments, multiple members, families, benefits, etc, that actually works. Eventually automation.
To get around the Metadata API limitation, we created two versions of the Membership Form Submission - AFTER Flow.
Can we remove the Membership Form Submission - AFTER - Create/Update MFS In favor of Membership Form Submission - AFTER - MFS Auditor. We can also rename it! (It is admittedly a bad name!)
The Campaign_Finder_Ran__c field on the Membership Form Submission Object can also be removed as it is no longer needed.
To get around the Metadata API limitation, we created two versions of the Membership Form Submission - AFTER Flow.
Can we remove the Membership Form Submission - AFTER - Create/Update MFS In favor of Membership Form Submission - AFTER - MFS Auditor. We can also rename it! (It is admittedly a bad name!)
The Campaign_Finder_Ran__c field on the Membership Form Submission Object can also be removed as it is no longer needed.