Enabling Local Name fields is a few clicks. The harder work is integrating them into the org''s data model and integrations.
- Open Person Name Field Display Options
Setup, Quick Find, Person Name Field Display Options. The configuration node opens.
- Enable Local Name fields
Check Enable Local Name fields. The setting unlocks the new fields on Account, Contact, Lead, and User.
- Add to page layouts
Edit the relevant page layouts to surface the new Local Name fields alongside the English Name fields.
- Update integrations
Coordinate with integration developers to map the Local Name fields from external systems. Document the mapping clearly.
- Train users
Explain to users in affected markets when to use the Local Name vs. English Name field. Most users default to entering both for new records.
- Configure search and report behavior
Verify that searching by either name representation finds the record. Build reports as appropriate per region.
- Local Name fields are not on by default. Multilingual orgs that skip the configuration lose the bilingual searchability benefit.
- Integration data hygiene is critical. Mistakenly loading English names into Local Name fields corrupts the bilingual model.
- Display options apply per profile or org. Mismatched configurations across markets confuse users; align the policy globally.
- Multi-byte characters in Local Name fields consume more storage. Plan storage estimates accordingly.