I am trying to think through my first FormAssembly form. It is a membership form. There may be an explicit renewal (via an ID in a hidden field), or it may be an implicit renewal, presented as new membership. Or it may be a new membership. It may be for an organization/account, or for a contact.
The connector is starting to feel like a nightmare. If lookup for the account fails, then create an account. If it's an individual membership, we first look up the contact, and if that doesn't work, the contact needs to be created and the household along with it.
Once that's all sorted, the opportunity, opportunityLineItems (oh yes!) and payment all need to be created. Based on what I understand of the connector, this part will need to be specifed several times depending on how the account and contact are looked up/created. If the account is found by lookup (all the steps for opportunity, OLI, payment), if the Contact is found by lookup (all the steps for opportunity, OLI, payment), if the account and contact are created anew (all the steps for opportunity, OLI, payment).
Is there a clear path through all of this? Linked forms or workflows or something? At this point, I'm considering just creating a custom object in Salesforce to receive all of the form data, then using Apex or Flow to handle the logic of locating and creating the records I need to complete the purchase in SF. It becomes difficult for the end user to, say, add a field for data collection, but if that field is mapped 3 places in the connector, it's not very user-serviceable to begin with. #FormAssembly Web Forms
Re-reading this, I though I should clarify what I mean by "implicit renewal" - that's just to say that some people will fill out the form as a new member, even though they have an existing account/contact and membership in our system.
