• #36832
    Salesforce | Aman Aman #4

    What are few Considerations about Salesforce Trigger?

    What are few Considerations about Salesforce Trigger ?


    Salesforce | shariq shariq #1

    upsert triggers fire both before and after insert or before and after update triggers as appropriate.
    merge triggers fire both before and after delete triggers for the losing records and before update triggers for the winning record only.
    Triggers that execute after a record has been undeleted only work with specific objects.
    Field history is not recorded until the end of a trigger. If you query field history in a trigger, you will not see any history for the current transaction.
    You can only use the webService keyword in a trigger when it is in a method defined as asynchronous; that is, when the method is defined with the @future keyword.
    A trigger invoked by an insert, delete, or update of a recurring event or recurring task results in a runtime error when the trigger is called in bulk from the Force.com API.
    Merge trigger doesn’t fire there own trigger instead they fire delete and update of loosing and winning records respectively.

Viewing 2 posts - 1 through 2 (of 2 total)

Please to reply to this topic.


We're not around right now. But you can send us an email and we'll get back to you, asap.


About Us

Forcetalks is a Salesforce collaboration platform for coders & developers, geeks & nerds, consultants & business heads, admins & architects, managers & marketers and of course the business owners. A community where you can learn from, where you can contribute to. For you. For Salesforce. Read More...

Copyright 2019 Forcetalks. All Right Reserved.

Log in with your credentials


Forgot your details?