Specifying Standard Objects

The Ant Migration Tool is retired with Spring ’24. The tool continues to function as-is for future API versions but isn’t updated with new functionality and isn’t supported. If Salesforce adds a new feature that is incompatible with Ant, the Ant Migration Tool won’t be updated to support it. To manage metadata changes, switch to Salesforce CLI for a modern, supported developer experience.

Note

To retrieve standard objects and/or custom fields on standard objects, you must name the component in package.xml. The following package.xml file will retrieve a single field EngineeringReqNumber__c, on the Case object, as well as the entire Account object.

1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns="http://soap.sforce.com/2006/04/metadata">
3    <types>
4        <members>Case.EngineeringReqNumber__c</members>
5        <name>CustomField</name>
6    </types>
7    <types>
8        <members>Account</members>
9        <name>CustomObject</name>
10    </types>
11    <version>68.0</version>
12</Package>

Custom objects and standard objects should be specified in the same <types> section, the one containing <name>CustomObject</name>.

Note