Ant Migration Tool Guide
jNote: 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.
Specifying Named Components
To retrieve a component, specify the type of component in the <name> element and declare each component to be retrieved or deployed in the <members> element. The following is a sample package.xml project manifest that names two custom objects to be retrieved or deployed:
1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns="http://soap.sforce.com/2006/04/metadata">
3 <types>
4 <members>MyCustomObject__c</members>
5 <members>MyHelloWorldObject__c</members>
6 <name>CustomObject</name>
7 </types>
8 <version>68.0</version>
9</Package>Some metadata components are sub-components of another component. This means you must dot-qualify the sub-component with the parent component name.
- CustomField
- Picklist
- RecordType
- Weblink
- ValidationRule
1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns="http://soap.sforce.com/2006/04/metadata">
3 <types>
4 <members>Opportunity.ValidationRuleName</members>
5 <name>ValidationRule</name>
6 </types>
7 <version>68.0</version>
8</Package>