Person accounts
This page only matters if your Salesforce organisation uses person accounts. If it does, a form that maps anything to Account has one extra decision to make.
Two Account entries in the picker
Section titled “Two Account entries in the picker”The mapping picker’s object list shows two Account entries: Account (a business account) and Person Account. Both create Account records, but they offer different fields, because the two kinds of account hold different information.
| Entry | Fields it offers |
|---|---|
| Person Account | The person fields (Person Email, Person Mobile, First Name, Last Name, Salutation, and any field you added to Contact), plus the ordinary Account fields a person account also has, such as Phone, Billing City and Owner |
| Account | Ordinary Account fields only. The person fields are hidden, because a business account cannot store them |
Picking Person Account also sets the form’s Account record type to Person Account. The picker tells you: Also sets this form’s Account record type to Person Account, saved with your next Save draft. If your organisation has more than one person record type, the picker first asks Which person record type does this form create?
This keeps the fields you map and the kind of account the form creates in step with each other.
The record type must be chosen, even with one active
Section titled “The record type must be chosen, even with one active”On a person-account organisation, an Account-mapped form must choose its record type before it can publish, even if only one Account record type is active. If nothing were chosen, each record would get the default record type of whoever processes the submission, so whether it became a business or a person account would be down to chance.
Choose it in Settings, under Record types.
Publishing is refused if a business Account form maps a person field. The message names the fields. To fix it, choose Person Account in Settings, or map those questions somewhere else.
Full name on a person account
Section titled “Full name on a person account”If a single full-name question is mapped to Account.Name, the name is split into First Name and Last Name when the form creates a person account, the same as on Contact. Ada Grace Lovelace becomes First Name Ada Grace and Last Name Lovelace. The picker marks that field split into First / Last so you know this will happen.
Matching stays within the same kind of account
Section titled “Matching stays within the same kind of account”A Person Account form only matches other person accounts. If it matches on, say, phone number, it will not update a business account that happens to have the same number. It creates a new person account and leaves the business account alone. See Matching: update instead of duplicate.
If processing fails with a field error
Section titled “If processing fails with a field error”The picker and the publish check prevent these two errors for forms built in the builder. You are only likely to see them on a form brought in another way, such as a blueprint import or a data load.
| The submission’s error says | What it means and how to fix it |
|---|---|
| Bad field names on insert or update, naming a person field | A person-only field is being written to a business account. Set the form’s Account record type to Person Account, or map those questions elsewhere |
Unable to create or update Name, with wording about security settings | Despite the wording, this is not a permissions problem. A full name is being written whole to a person account, which stores First Name and Last Name instead. Choose the Person Account record type and the name is split for you |