The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Building a household intake workflow from FormAssembly into Salesforce (opens in a new tab)

You will see how to model a variable-length child intake as a staging parent with a Master-Detail child Custom Object, and how to avoid the flat-file and metadata-caching faults that break such integrations.

Why read this

The reader gets a worked example of a real external form pipeline.

Denormalized parent

  • Member_1 to Member_10 columns
  • Blank fields sent as nulls
  • Submission rejected

Normalized model

  • Household_Submission__c parent
  • Household_Member__c children
  • Master-Detail relationship
The flat parent layout failed, and normalising to a Master-Detail child model fixed it

The author argues that public intake forms are better handled by a dedicated external form engine than by a Salesforce Experience Cloud site, which needs heavy configuration and guest-user sharing management. They test the new FormAssembly platform, which models data collection as an end-to-end workflow with an AI assistant, Fai, that builds the form from a plain-language specification.

For a household intake where the number of members varies, Fai offered three designs and the author chose fixed member sections with conditional visibility, so that the required sections match the declared household count. The data then goes to a staging Custom Object rather than directly to Contact or Account, to avoid creating duplicates from unverified input.

The article records two pitfalls. Denormalized numbered member columns on the parent produced null payloads that caused the submission to be rejected, so the schema was normalized to a Household_Submission__c parent and a Household_Member__c child joined by Master-Detail. A deleted lookup field also remained in the connector’s cached metadata, and updating the field mapping to the new API name resolved the error.

Read the original at Salesforce Break (opens in a new tab)

Worth reading?