Metadata API Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Introduction to Metadata API
Understanding Metadata API
Use Cases for Metadata API
Move Metadata from Production to Your Local File System
Move Metadata Changes to and from a Scratch Org
Move Metadata to a Sandbox at Integration Points
Deploy Metadata to Production
Move Metadata for Production-Level Changes
Make Large Metadata Configuration Changes
Release Notes
Metadata API Developer Tools
Supported Salesforce Editions
Metadata API Edit Access
Development Platforms
Standards Compliance
Metadata API Support Policy
API End-of-Life Policy
Related Resources
Quick Start: Metadata API
Build Client Applications for Metadata API
Using Metadata API
Reference
Appendices
PDF

Make Large Metadata Configuration Changes

Metadata API is better suited than other APIs for deploying large changes to your Salesforce org.

Metadata API deploy() and retrieve() calls are file-based and therefore asynchronous. With synchronous commands, large configuration changes require unreasonably long load times. Instead, deploy and retrieve calls begin an asynchronous process that notifies you when it’s complete. Because file-based calls are asynchronous, Metadata API can also handle a queue of deploy requests.