NameSettings

Enables or disables the formal name, middle name, and suffix attributes for the following person objects: Contact, Lead, Person Account, and User.This type extends the Metadata metadata type and inherits its fullName field.

In the package manifest, all organization settings metadata types are accessed using the “Settings” name. See Settings for more details.

File Suffix and Directory Location

NameSettings values are stored in a single file named Name.settings in the settings folder. The .settings files are different from other named components because there is only one settings file for each settings component.

Version

NameSettings components are available in API version 31.0 and later.

Fields

Field Name	Field Type	Description
enableInformalName	boolean	Indicates whether informal names are enabled (`true`) or disabled (`false`) for person objects. Available in API version 48.0 and later.
enableMiddleName	boolean	Indicates whether middle names are enabled (`true`) or disabled (`false`) for person objects.
enableNameSuffix	boolean	Indicates whether suffixes are enabled (`true`) or disabled (`false`) for person objects.

Declarative Metadata Sample Definition

The following is an example of a NameSettings component.

1<?xml version="1.0" encoding="UTF-8"?>
2<NameSettings xmlns="http://soap.sforce.com/2006/04/metadata">
3    <enableInformalName>false</enableInformalName>
4    <enableMiddleName>true</enableMiddleName>
5    <enableNameSuffix>false</enableNameSuffix>
6</NameSettings>

The following is an example package.xml manifest that references the NameSettings definitions.

1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns="http://soap.sforce.com/2006/04/metadata">
3    <types>
4        <members>Name</members>
5        <name>Settings</name>
6    </types>
7    <version>31.0</version>
8</Package>

Wildcard Support in the Manifest File

The wildcard character * (asterisk) in the package.xml manifest file doesn’t apply to metadata types for feature settings. The wildcard applies only when retrieving all settings, not for an individual setting. For details, see Settings. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.

Metadata API Developer Guide