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.
ApexComponentMember
Supported SOAP API Calls
create(), delete(), describeSObjects(), query(), retrieve(), update(), upsert()
Special Access Rules
As of Spring ’20 and later, to access ApexComponentMember, users must have both the View All Data and Customize Application permissions.
Supported REST API HTTP Methods
Query, GET, POST, PATCH, DELETE
Fields
| Field Name | Details |
|---|---|
| Body |
|
| Content |
|
| ContentEntityId |
|
| FullName |
|
| LastSyncDate |
|
| Metadata |
|
| MetadataContainerId |
|
Usage
To edit, save, or compile a Visualforce component, create an ApexComponentMember object that references it. To create a Visualforce component, use the REST API or the Metadata API.
Visualforce pages and components are often dependent on each other for functionality. To successfully save and compile a group of related source files, put the corresponding ApexComponentMember and ApexPageMember objects in a single MetadataContainer object.
Each ApexComponentMember object can only refer to a single MetadataContainer object. Multiple ApexComponentMember objects can refer to the same MetadataContainer object.