search

benedwards44 / packagebuilder

Django + Heroku application for building a package.xml of your Salesforce Org
https://packagebuilder.herokuapp.com
MIT License
104 stars 81 forks source link

Disable wildcards on types that do not support wildcards #31

Open gwynnebaer opened 4 years ago

gwynnebaer commented 4 years ago

FEATURE REQUEST: There are several caveats, exceptions, and other issues with wildcard usage, and the tool does not distinguish these exceptions or limitations.

Examples CustomObject - Note how you work with the standard Account object by specifying it as a member of a CustomObject type. However, you cannot use an asterisk wildcard to work with all standard objects; each standard object must be specified by name. AccountSettings - The wildcard character doesn’t apply to metadata types for feature settings, like AccountSettings. AnalyticSnapshot - This metadata type doesn’t support the wildcard character * (asterisk) in the package.xml manifest file.

etc. I can list all the exceptions, not sure if that is worth it. At the present, the wildcard option is not particularly useful for those who want to scrape every last bit of data from the Metadata API.

sfdcale commented 4 years ago

@gwynnebaer I am not sure I fully understand the request. This tool doesn't consume package.xml but instead it produces package.xml and the package.xml it produces will not have any wildcard.

gwynnebaer commented 4 years ago

The option to create a package.xml using wildcards does not respect the caveats, exceptions, and limitations of the Metadata API. It instead creates a package.xml file with wildcards even on metadata that does not support wildcards, which renders the package.xml file less useful if not unusable.

sfdcale commented 4 years ago

My mistake. Looks like wildcard option is added recently.