Considerations for Using Merge Fields in Validation Rules for Person
Accounts
A merge field incorporates values from a record. You can add merge fields to an email
template, mail merge template, custom link, or formula. If your person account validation
rules include merge fields, here are some things to keep in mind.
Required Editions
|
Business accounts available in: both Salesforce Classic and Lightning
Experience
Business accounts available in: All Editions
|
|
Person accounts available in: Both Salesforce Classic and Lightning
Experience
Person accounts available in Professional, Enterprise,
Performance, Unlimited, and Developer Editions
|
- The list of available merge fields depends on the type of data that
you’re working with.
- To define a validation rule that applies only to person
accounts, use the
IsPersonAccount merge
field. For example, Account.City = “San
Francisco” verifies that a business or person
account’s city is San Francisco, while IsPersonAccount ( Account.City = “San Francisco”)
verifies that a person account’s city is San Francisco.
- Handle person account and business account names
separately in account validation rules.
- For business accounts, use the
Name
merge field.
- For person accounts, use the
FirstName and LastName merge fields.
- Birthdate,
Email, and other fields that are only supported for
person accounts are available as merge fields in account validation rules. When
you use one of those merge fields, business account records are processed as if
those fields have blank values.
