---
schema_version: "1"
id: 5979e5a9858e9f84bd93f0cc54d682c4d28d6e1ad91aecf2fec1aec1eb6f50f1
title: NameSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_namesettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_namesettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 41b563ab16fade72d0bd1103e5313277645179b9e6a39e57aad840dac90dc2d8
description: "Enables or disables the formal name, middle name, and suffix attributes for these person objects: Contact, Lead, Person Account, and User. This type extends the Metadata metadata type and inherits its fullName field."
---
# NameSettings

Enables or disables the formal name, middle name, and suffix attributes for these 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](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_settings.htm "Represents the organization settings related to a feature. For example, your password policies, session settings and network access controls are all available in the SecuritySettings component type.") for details.

You can’t enable local name fields programmatically via the Metadata API. For more information about enabling local fields, see [Local Name Fields](https://help.salesforce.com/s/articleView?id=xcloud.admin_local_name_fields.htm&language=en_US "HTML (New Window)") and [Enable ‘Local Name’ Fields](https://help.salesforce.com/s/articleView?id=000386837&type=1&language=en_US "HTML (New Window)").

## 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’s 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 | Reserved for internal use. 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

This example shows a NameSettings component.

<?xml version="1.0" encoding="UTF-8"?>
<NameSettings xmlns="http://soap.sforce.com/2006/04/metadata">
    <enableMiddleName\>true</enableMiddleName\>
    <enableNameSuffix\>false</enableNameSuffix\>
</NameSettings\>

This example package.xml manifest references the NameSettings definitions.

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types\>
        <members\>Name</members\>
        <name\>Settings</name\>
    </types\>
    <version\>31.0</version\>
</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](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/meta_settings.htm). For information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/file_based_zip_file.htm).