standard objects listed under CustomObject
When using contents=Selected, standard objects, e.g., Account, etc., are displayed under the CustomObject branch. There's no StandardObject branch available.
Comments (8)
-
-
repo owner -
assigned issue to
- changed version to 1.2.1
-
assigned issue to
-
repo owner This will be fixed in the next patch. Salesforce has clarified the use of wildcards for the CustomObject metadata type (which includes customizations for standard objects):
https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_types_list.htm
Basically for access to arbitrary contents of custom/standard objects, wildcards should not be used.
-
Scott -
I don't know about wildcards in general, but I know I've seen other IDEs generate this section by listing all the standard object explicitly, then using the wildcard at the end. This has the effect of pulling down both all custom and standard objects, without making you update the package.xml every time you add a new object. It also pulls down all fields on those objects if you don't use the custom fields type.
-
repo owner Yeah, I remembered exactly that last night. I'll see if I can work that into this next patch.
-
repo owner FYI, I'm separating an effective fix for this from efficient authoring of the underlying package.xml. Version 1.2.1 will include a fix that treats CustomObject as a non-wildcard metadata type. In a subsequent release I'll have it treat CustomObject as wildcard for true custom objects and explicit for standard objects.
-
repo owner - changed status to resolved
-
repo owner - changed component to Metadata Deployment/Retrieval/Removal
- Log in to comment
I also noticed this. I selected All/Package and when I retrieve the metadata from the server, the package.xml file doesn't list any standard objects:
Note that Salesforce doesn't pull back standard objects unless they're specifically listed in this section.