Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
DataSourceBundleDefinition
Parent Type
File Suffix and Directory Location
DataSourceBundleDefinition components have the suffix .dataSourceBundleDefinition and are stored in the dataSourceBundleDefinitions folder.
Version
DataSourceBundleDefinition components are available in API version 52.0 and later.
Special Access Rules
You need Data 360 permission to access this object.
Fields
Declarative Metadata Sample Definition
The following is an example of a DataSourceBundleDefinition component.
1<?xml version="1.0" encoding="UTF-8"?>
2<DataSourceBundleDefinition xmlns="http://soap.sforce.com/2006/04/metadata">
3 <dataPlatform>Salesforce_Sales_and_Service_Cloud</dataPlatform>
4 <isMultiDeploymentSupported>true</isMultiDeploymentSupported>
5 <bundleVersion>1</bundleVersion>
6 <masterLabel>b2</masterLabel>
7</DataSourceBundleDefinition>The following is an example package.xml that references the previous definition.
1<types>
2 <members>b2</members>
3 <name>DataSourceBundleDefinition</name>
4</types>Wildcard Support in the Manifest File
This metadata type supports 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.