Local Name
Local Name in Salesforce is the localized version of a person''s or account''s name in a non-English alphabet, stored alongside the English-equivalent name field.
Definition
Local Name in Salesforce is the localized version of a person''s or account''s name in a non-English alphabet, stored alongside the English-equivalent name field. The standard objects Account, Contact, Lead, and User all have Local Name field variants (Local Name, First Local Name, Last Local Name) that admins enable when the org operates in markets where customers and employees go by names that have both an English-transliterated form and a native-script form (Chinese, Japanese, Korean, Russian, Arabic). The fields store the native-script value while the main Name field holds the English transliteration.
Local Name fields are essential in Asian markets and any other market where bilingual record-keeping is the norm. A Japanese customer named TARO YAMADA in English has a local name written in kanji. The customer-facing experience uses the local name; the internal Salesforce search and reporting can use either. Without Local Name fields, the org has to pick one alphabet (typically English) and lose the local representation, which hurts customer experience and search accuracy in those markets.
How Local Name fields support multilingual Salesforce orgs
Enabling Local Name fields
Local Name fields are not on by default; admins enable them via Setup, User Interface, Person Name Field Display Options. Once enabled, the Account, Contact, Lead, and User objects expose Local Name fields that admins add to page layouts. Each name field becomes a pair: the English-transliterated value and the local-script value.
Person Name Field Display Options
The Setup node lets admins choose how name fields display across Lightning Experience. Options include English Only (default), English with Local, Local with English, and Local Only. The choice applies per user profile or per org, depending on the configuration. Most multilingual orgs default to English with Local for desktop and switch to Local Only on customer-facing portals.
Search across both name representations
Salesforce search indexes both English and Local Name fields. A user searching for the English name finds the record; a user searching for the local-script name finds the same record. This is the most-important benefit of Local Name fields: bilingual searchability without duplicate records.
Multi-currency and multi-language alignment
Local Name fields pair naturally with multi-currency and multi-language orgs. A Japan-based subsidiary using Local Name with English alongside the Japanese yen currency and Japanese UI language produces a cohesive Japanese-language experience. The three settings (currency, language, name display) should be aligned for the target user persona.
Integration data hygiene
Integrations with external systems (CRM, ERP, billing) must agree on how Local Name maps. The most common bug is loading the English name into the Local Name field or vice versa; this corrupts searchability and customer experience. Document the field mapping per integration.
Reporting and analytics
Reports can group by either English Name or Local Name. The choice depends on the audience: an English-speaking executive report uses English Name; a Japan-team report uses Local Name. Salesforce supports both as report-eligible fields.
Person Account considerations
Person Accounts (the B2C account variant) get the same Local Name treatment. The Person Account combines Account and Contact, so the Local Name fields apply to both representations. Salesforce keeps the two synchronized automatically.
Enable and configure Local Name fields
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.
Trust & references
Cross-checked against the following references.
- Person Name Field Display OptionsSalesforce Help
- Salesforce Supported LanguagesSalesforce Help
Straight from the source - Salesforce's reference material on Local Name.
- Locale and Language SettingsSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Local Name?
Q2. When are Local Names valuable?
Q3. What objects support Local Name fields?
Discussion
Loading discussion…