Activity Forums Salesforce® Discussions What sObject properties doesn't cause trigger to fire in salesforce?

  • PRANAV

    Member
    October 3, 2016 at 6:27 am

    Hi Mohit,

    There are many operations like some system bulk operations don't invoke triggers:

    • Cascading delete operations.
    • Cascading updates of child records that are reparented as a result of a merge operation
    • Changing a user's default division with the transfer division option checked
    • Changes to the following objects:
      BrandTemplate
      MassEmailTemplate
      Folder
    • Mass address updates
    • Mass approval request transfers
    • Mass campaign status changes
    • Mass division transfers
    • Mass email actions
    • Managing price books
    • Modifying custom field data types
    • Renaming or replacing picklists
    • Update account triggers don't fire before or after a business account record type is changed to person account (or a person account record type is changed to business account.)
    • Inserts, updates, and deletes on person accounts fire Account triggers, not Contact triggers.
    • Content pack operations involving the ContentVersion object, including slides and slide autorevision, don't invoke triggers.
    • Triggers on the Attachment object don’t fire when:
      the attachment is created via Case Feed publisher.
      the user sends email via the Email related list and adds an attachment file.

    Hope this helps you.

    Thanks

Log In to reply.

Popular Salesforce Blogs

Popular Salesforce Videos