What are a couple of Considerations about Trigger?

devquora
devquora

Posted On: Feb 22, 2018

 

  1. Upsert triggers fire both before and after the insert or when update triggers as proper.
  2. Merge triggers fires both
  3. Field history isn’t recorded until the trigger end. If you question field history in a trigger, you won’t perceive any history for the present transaction.
  4. You can just utilize the webService keyword in the trigger when it is in a technique characterized as offbeat; that is, the point at which the strategy is described with the @future keyword.
  5. A trigger conjured by an insert, update or delete of the recurring event or repeating task brings about a runtime error when the trigger is brought in bulk from the Force.com API.
  6. Merge trigger doesn’t fire their own trigger rather they fire update or delete of losing and winning records individually.

    Related Questions

    Please Login or Register to leave a response.

    Related Questions

    Apex Interview Questions

    Tell me something about Abstract Class?

     The abstract classes in Salesforce Apex are the classes that involve at least one dynamic strategy. A conjectural meth..

    Apex Interview Questions

    Clarify a couple of considerations required for the Static Keyword in Apex.

     Here are a couple of considerations required for the Static keyword in Apex.  You cannot make an Apex class static..

    Apex Interview Questions

    Can you state some o the uses of APEX?

    fabricates proficient looking web applications that are both quick and secure. Keeps running on and lives in the Oracle..