Which Metadata Components are Accessible?

The following table lists all of the metadata types that can be retrieved or deployed with the Metadata API, the XML name used in the package.xml file for the metadata type, the folder the component is retrieved into, whether or not the component may be retrieved with the wildcard (*) symbol in package.xml, and notes about this component, where applicable.

Component XML <name> Metadata Type Folder * Notes
Account Criteria Based Sharing Rule criteriaBasedRules accountSharingRules yes AccountCriteriaBasedSharingRule is represented as criteriaBasedRules, contained in the AccountSharingRules component.
Account Owner Sharing Rule ownerRules accountSharingRules yes AccountOwnerSharingRule is represented as ownerRules, contained in the AccountSharingRules component.
Action Override ActionOverride objects no This type is retrieved or deployed as part of a custom object file. You must dot-qualify the object name before the component name.
Account Territory Sharing Rule rules accountTerritorySharingRules yes AccountTerritorySharingRule is represented as rules, contained in the AccountTerritorySharingRules component.
Analytic Snapshot AnalyticSnapshot analyticsnapshots no
Apex class ApexClass classes yes
Article Type ArticleType objects yes
Visualforce component ApexComponent components yes
Visualforce page ApexPage pages yes
Apex trigger ApexTrigger triggers yes
Business process BusinessProcess objects no This type is retrieved or deployed as part of a custom object file. You must dot-qualify the object name before the component name.
Campaign Criteria Based Sharing Rule criteriaBasedRules campaignSharingRules yes CampaignCriteriaBasedSharingRule is represented as criteriaBasedRules, contained in the CampaignSharingRules component.
Campaign Owner Sharing Rule ownerRules campaignSharingRules yes CampaignOwnerSharingRule is represented as ownerRules, contained in the CampaignSharingRules component.
Case Criteria Based Sharing Rule criteriaBasedRules caseSharingRules yes CaseCriteriaBasedSharingRule is represented as criteriaBasedRules, contained in the CaseSharingRules component.
Case Owner Sharing Rule ownerRules caseSharingRules yes CaseOwnerSharingRule is represented as ownerRules, contained in the CaseSharingRules component.
Contact Criteria Based Sharing Rule criteriaBasedRules contactSharingRules yes ContactCriteriaBasedSharingRule is represented as criteriaBasedRules, contained in the ContactSharingRules component.
Contact Owner Sharing Rule ownerRules contactSharingRules yes ContactOwnerSharingRule is represented as ownerRules, contained in the ContactSharingRules component.
Custom Object Criteria Based Sharing Rule criteriaBasedRules customObjectSharingRules no CustomObjectCriteriaBasedSharingRule is represented as criteriaBasedRules, contained in the CustomObjectSharingRules component.
Custom Object Owner Sharing Rule ownerRules customObjectSharingRules no CustomObjectOwnerSharingRule is represented as ownerRules, contained in the CustomObjectSharingRules component.
Custom application CustomApplication applications yes
Custom field CustomField objects no Custom fields are retrieved or deployed as part of a custom object file. You must dot-qualify the object name before the component name. Individual custom fields cannot be retrieved with the wildcard (*) symbol, but must be explicitly named in package.xml, unless their object is named in the CustomObject section.
Custom label CustomLabels labels yes Custom labels that can be localized for use in different languages, countries, and currencies.
Custom object or standard object CustomObject objects yes Standard objects cannot be retrieved with the wildcard (*) symbol, but must be explicitly named in package.xml, and only custom fields and standard picklist fields are included.
Custom object translation CustomObjectTranslation objectTranslations yes
Custom page web link CustomPageWebLink weblinks yes Web links are defined in a home page component.
Custom site CustomSite sites yes
Custom tab CustomTab tabs yes
Dashboard Dashboard dashboards no
Data Categories DataCategoryGroup datacategorygroups yes Includes a category group and its categories.
Document Document document no
Email template EmailTemplate email no
Entitlement Template EntitlementTemplate entitlementTemplates yes
Field set FieldSet objects yes
Flow Flow flows yes A .flow file is an XML representation of a flow definition.
Group Group groups yes
Home page component HomePageComponent homePageComponents yes
Home page layout HomePageLayout homePageLayouts yes
Page layout Layout layouts yes
Letterhead Letterhead letterhead no
List view ListView objects no This type is retrieved or deployed as part of a custom object file. You must dot-qualify the object name before the component name.
Lookup filter NamedFilter objects no This type is retrieved or deployed as part of a custom object file. You must dot-qualify the object name before the component name.
Lead Criteria Based Sharing Rule criteriaBasedRules leadSharingRules yes LeadCriteriaBasedSharingRule is represented as criteriaBasedRules, contained in the LeadSharingRules component.
Lead Owner Sharing Rule ownerRules leadSharingRules yes LeadOwnerSharingRule is represented as ownerRules, contained in the LeadSharingRules component.
Opportunity Criteria Based Sharing Rule criteriaBasedRules opportunitySharingRules yes OpportunityCriteriaBasedSharingRule is represented as criteriaBasedRules, contained in the OpportunitySharingRules component.
Opportunity Owner Sharing Rule ownerRules opportunitySharingRules yes OpportunityOwnerSharingRule is represented as ownerRules, contained in the OpportunitySharingRules component.
Permission set PermissionSet permissionsets yes The contents of a permission set retrieved depends on the contents of the organization. For example, permission sets only include field-level security for fields included in custom objects returned at the same time as the permission sets.
Portal Portal portals yes
Profile Profile profiles yes The contents of a profile retrieved depends on the contents of the organization. For example, profiles will only include field-level security for fields included in custom objects returned at the same time as the profiles.
Queue Queue queues yes
Record type RecordType objects yes This type is retrieved or deployed as part of a custom object file. You must dot-qualify the object name before the component name.
Remote site setting RemoteSiteSetting remoteSiteSettings yes
Report Report reports no
Report type ReportType reportTypes yes Custom report types allow you to build a framework from which users can create and customize reports.
Role Role roles yes
Scontrol Scontrol scontrols yes
Sharing reason SharingReason objects no This type is retrieved or deployed as part of a custom object file. You must dot-qualify the object name before the component name.
Sharing recalculation SharingRecalculation objects no This type is retrieved or deployed as part of a custom object file. You must dot-qualify the object name before the component name.
Static resource StaticResource staticResources yes
Territory Territory territories yes
Translation Workbench Translations translations yes
Validation rule ValidationRule objects no This type is retrieved or deployed as part of a custom object file. You must dot-qualify the object name before the component name.
Web link Weblink objects no This type is retrieved or deployed as part of a custom object file. You must dot-qualify the object name before the component name.
Workflow Workflow workflows yes A .workflow file is a container for the individual workflow components associated with an object, including WorkflowAlert, WorkflowFieldUpdate, WorkflowOutboundMessage, WorkflowRule, and WorkflowTask.

Not everything in a Salesforce organization is available as a metadata component. With each release of Salesforce, more and more metadata components are added to the Metadata API.

The following components cannot be retrieved or deployed in the Metadata API, and changes to them (in a production organization or development environment) require manual migration:

© Copyright 2000–2012 salesforce.com, inc. All rights reserved.
Various trademarks held by their respective owners.