---
schema_version: "1"
id: b7687393566710c65fc4deb371e18fa7fd443aab52feeccba8686c4a03027bad
title: CustomerDataPlatformSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_customerdataplatformsettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_customerdataplatformsettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 0f95513034e066b0bb629e5892f66095f5f3bc08b46c6bf344c734364b026332
description: Represents an org's Data 360 settings.
---
# CustomerDataPlatformSettings

Represents an org's Data 360 settings.

## 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

CustomerDataPlatformSettings values are stored in the CustomerDataPlatformSettings.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

CustomerDataPlatformSettings components are available in API version 48.0 and later.

## Special Access Rules

## Fields

| Field Name | Description |
| --- | --- |
| enableCustomerDataPlatform | 
Field Type

boolean

Description

Indicates whether an org has Data 360 enabled (true) or not (false).



 |

## Declarative Metadata Sample Definition

The following is an example of a CustomerDataPlatformSettings component.

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

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\>CustomerDataPlatform</members\>
    <name\>Settings</name\>
  </types\>
  <version\>55.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.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 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.").