---
schema_version: "1"
id: 64d0984e437a89e2b1414f548ffa50b6dee55990cafde69d32ea0ccc16a37975
title: ExternalServicesSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_externalservicessettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_externalservicessettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 37dbb51e3d403c86057322fd0d054b56fab56f7932af855eb4753dade6af50b4
description: Represents settings for an External Services registration.
---
# ExternalServicesSettings

Represents settings for an External Services registration.

## Parent Type and Manifest Access

This type extends the [Metadata](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/metadata.htm "The base class for all metadata types. You can’t edit this object. A component is an instance of a metadata type.") metadata type and inherits its fullName field.

In the package manifest, all the settings metadata types for the org 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 more details.

## File Suffix and Directory Location

ExternalServicesSettings values are stored in the externalServicesSettings.settings file 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

ExternalServicesSettings components are available in API version 47.0 to 55.0. This metadata type is removed in version 56.0 and later.

As of Winter ’23, External Services automatically validates the schema and provides detailed messages for any errors in the UI at registration time so that you can make corrections. See [Register an External Service](https://help.salesforce.com/s/articleView?id=platform.external_services_register.htm&type=5&language=en_US "HTML (New Window)") in Salesforce Help.

## Fields

| Field Name | Description |
| --- | --- |
| enableIgnoreUnsupportedOperations | 
Field Type

boolean

Description

Indicates whether your registration should ignore and filter out unsupported schema operations rather than fail the entire registration (true), or whether a specification with invalid schema operations can't be registered successfully (false). Detailed schema errors pertaining to unsupported operations are shown only if this flag is false.



 |

## Declarative Metadata Sample Definition

The following is an example of an ExternalServicesSettings component.

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

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

<types\>
    <members\>ExternalServices</members\>
    <name\>Settings</name\>
  </types\>

## Wildcard Support in the Manifest File

This metadata type doesn’t support the wildcard character \* (asterisk) in the package.xml manifest file. For information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/file_based_zip_file.htm "The deploy() and retrieve() calls are used to deploy and retrieve a .zip file. Within the .zip file is a project manifest (package.xml) that lists what to retrieve or deploy, and one or more XML components that are organized into folders.").