No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
Newer Version Available
ApexTriggerMember
Represents the working copy of an Apex trigger for editing, saving or compiling in a MetadataContainer.
Supported SOAP API Calls
create(), delete(), describeSObjects(), query(), retrieve(), update(), upsert()
Supported REST API HTTP Methods
Query, GET, POST, PATCH, DELETE
Fields
| Field Name | Details |
|---|---|
| FullName |
|
| Body |
|
| Content |
|
| ContentEntityId |
|
| LastSyncDate |
|
| Metadata |
|
| MetadataContainerId |
|
| SymbolTable |
|
Usage
To edit, save, or compile an Apex trigger, create an ApexTriggerMember object that references it. To create a new trigger, use the Force.com REST API or the Metadata API.
Apex triggers and classes are often dependent on each other for functionality. For example, a method in one class can call a method in another class. If source file A is dependent on modified source file B and you try to save and compile source file A before you’ve saved the changes to source file B, the compiler will throw an error. To successfully save and compile a group of related source files, put the corresponding ApexTriggerMember and ApexClassMember objects in a single MetadataContainer object. Use ContainerAsyncRequest to send the MetadataContainer to the application server.
Each ApexTriggerMember object can only refer to a single MetadataContainer object. Multiple ApexTriggerMember objects can refer to the same MetadataContainer object.