---
schema_version: "1"
id: 04065495a0d5803a47e8455ab46682a303c076a67274062a7c48a6f5146fa01b
title: DeploymentSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_deploymentsettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploymentsettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 3e43371a73cdb6e4477153cc40d5eafb5e1db576a4ca7e8c588470ccffdd3e65
description: Represents the settings affecting how deployments behave in the org. This type extends the Metadata metadata type and inherits its fullName field.
---
# DeploymentSettings

Represents the settings affecting how deployments behave in the org. 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.

## File Suffix and Directory Location

DeploymentSettings values are stored in the Deployment.settings file in the settings directory. The .settings files are different from other named components, because there is only one settings file for each settings component.

## Version

DeploymentSettings components are available in API version 47.0 and later.

## Fields

<table class="featureTable sort_table" summary="">




          <thead class="thead sorted" align="left">
            <tr>
              <th class="featureTableHeader  " id="d369490e104">Field Name</th>

              <th class="featureTableHeader  " id="d369490e107">Field Type</th>

              <th class="featureTableHeader  " id="d369490e110">Description</th>

              <th class="featureTableHeader  " id="d369490e113"></th>

            </tr>

          </thead>

          <tbody class="tbody">
            <tr>
              <td class="entry" headers="d369490e104" data-title="Field Name"><span class="keyword parmname">doesSkipAsyncApexValidation</span></td>

              <td class="entry" headers="d369490e107" data-title="Field Type">boolean</td>

              <td class="entry" headers="d369490e110" data-title="Description">Indicates whether deployments from this org skip asynchronous Apex validations
                (<samp class="codeph nolang">true</samp>) or not (<samp class="codeph nolang">false</samp>). The default value is <samp class="codeph nolang">true</samp>.<p class="p">Set this field to <samp class="codeph nolang">false</samp>
                  when an Apex class in the package you’re deploying is used by an Apex batch job
                  that could run during the deployment. The deployment of a package containing an
                  Apex class that is used by a running batch job fails without
                  validation.</p>
              </td>

              <td class="entry" headers="d369490e113" data-title=""></td>

            </tr>

          </tbody>

        </table>

## Declarative Metadata Sample Definition

The following is an example of a DeploymentSettings component.

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

The following is an example package.xml that references the previous definition.

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
   <types\>
      <members\>Deployment</members\>
      <name\>Settings</name\>
   </types\>
   <version\>47.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).