Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
ContainerAsyncRequest
Supported SOAP API Calls
create(), describeSObjects(), query(), retrieve()
Supported REST API HTTP Methods
Query, GET, POST
Special Access Rules
As of the Spring '20 release, to access ContainerAsyncRequest you must have both the View All Data and Customize Application user permissions.
Fields
| Field Name | Details |
|---|---|
| DeployDetails |
|
| ErrorMsg |
|
| IsCheckOnly |
|
| IsRunTests |
|
| MetadataContainerId |
|
| MetadataContainerMemberId |
|
| State |
|
Usage
When you deploy a ContainerAsyncRequest, you must specify whether to save the compiled entities:
- To compile entities without saving, set the request to IsCheckOnly=true. This option is only supported if a MetadataContainerMember is specified. A single MetadataContainerMemberId can’t be compiled without saving.
- To compile and save entities to your organization, set the request to IsCheckOnly=false.
If the compile succeeds, the SymbolTable field is updated on each object in the specified MetadataContainer. If the save or compile fails and a SymbolTable field cannot be updated, the field is cleared. If there is an outstanding save request, all updates, inserts, and deployments fail.
To terminate a queued deployment, set the State field to Aborted.