standard objects listed under CustomObject

Issue #72 resolved
Petr Švestka created an issue

When using contents=Selected, standard objects, e.g., Account, etc., are displayed under the CustomObject branch. There's no StandardObject branch available.

Comments (7)

  1. Nathen Drees

    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.

  2. Nathen Drees

    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.

  3. Scott Wells repo owner

    Yeah, I remembered exactly that last night. I'll see if I can work that into this next patch.

  4. Scott Wells 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.

  5. Log in to comment