What all can be deployed using metadata API?
Any metadata that is supported by the API can be deployed between orgs using a deployment tool such as Ant or Gearset….The API supports the vast majority of Salesforce metadata, including:
- Apex classes.
- Communities.
- Custom objects.
- Dashboards.
- Documents.
- Email templates.
- Flows.
- Layouts.
What is metadata deployment?
Use the deploy() and retrieve() calls to move metadata (XML files) between a Salesforce organization and a local file system. The Ant Migration Tool uses the deploy() and retrieve() calls to move metadata. If you use these tools, interaction with Metadata API is seamless and invisible.
What is metadata API?
Metadata API Functionality Use Metadata API to deploy, retrieve, create, update, or delete customization information, such as custom object definitions and page layouts. To create, retrieve, update, or delete records such as accounts or leads, use SOAP API or REST API. You can move metadata with one of two ways.
What is the API used during deployment salesforce?
Salesforce continues to support the use of checkStatus() when using deploy() with API version 28.0 or earlier. The package. xml file is a project manifest that lists all the components that you want to retrieve or deploy.
How to deploy Salesforce communities via the metadata API?
Including these alongside Network, CustomSite and SiteDotCom in your deployment will ensure that the look and feel of your community is migrated to the target org. Deploying changes to communities is very similar to deploying new communities, just without the initial prerequisite steps.
Which is version 40 of the metadata API?
Version 40 of the metadata API includes a NetworksEnabled preference in OrgPreferenceSettings – if communities are enabled in the source and not in the target, then you’ll see this appear in the diff view in Gearset for the OrgPreference item.
When to use junction metadata in API version 39?
In API version 39.0 and earlier, retrieving or deploying permission set metadata returns only app and system permissions assigned to the permission set. Junction metadata (such as Apex, CRUD) are included only if the metadata for the related component is also included in the package definition.
When to change the name of a deployment?
If you run another deployment and give it the same name, the earlier entry is replaced with the current deployment. If you want to maintain unique entries in the deployment history, give each deployment a unique name.