• #31227
    Forcetalks

    What are the best practices for Salesforce triggers?

    What are the best practices for Salesforce triggers?

     

    #31234
    Forcetalks

    Hi Madhulika,

    Trigger Best Practices:-

    1. There should only be one trigger for each object.
    2. Avoid complex logic in triggers. To simplify testing and reuse, triggers should delegate to Apex classes which contain the actual execution logic.
    3. Bulkify any “helper” classes and/or method
    4. Triggers should be “bulkified” and be able to process up to 200 records for each call.
    5. Execute DML statements using collections instead of individual records per DML statement.
    6. Use Collections in SOQL “WHERE” clauses to retrieve all records back in the single query
    7. Use a consistent naming convention including the object name (e.g., AccountTrigger)

    Thanks.

    #34853
    Salesforce | shariq shariq #1
    Forcetalks

    Hi,

    1) One Trigger Per Object
    A single Apex Trigger is all you need for one particular object. If you develop multiple Triggers for a single object, you have no way of controlling the order of execution if those Triggers can run in the same contexts

    2) Logic-less Triggers
    If you write methods in your Triggers, those can’t be exposed for test purposes. You also can’t expose logic to be re-used anywhere else in your org.

    3) Context-Specific Handler Methods
    Create context-specific handler methods in Trigger handlers

    4) Bulkify your Code
    Bulkifying Apex code refers to the concept of making sure the code properly handles more than one record at a time.

    5) Avoid SOQL Queries or DML statements inside FOR Loops
    An individual Apex request gets a maximum of 100 SOQL queries before exceeding that governor limit. So if this trigger is invoked by a batch of more than 100 Account records, the governor limit will throw a runtime exception

    6) Using Collections, Streamlining Queries, and Efficient For Loops
    It is important to use Apex Collections to efficiently query data and store the data in memory. A combination of using collections and streamlining SOQL queries can substantially help writing efficient Apex code and avoid governor limits

    7) Querying Large Data Sets
    The total number of records that can be returned by SOQL queries in a request is 50,000. If returning a large set of queries causes you to exceed your heap limit, then a SOQL query for loop must be used instead. It can process multiple batches of records through the use of internal calls to query and queryMore

    8) Use @future Appropriately
    It is critical to write your Apex code to efficiently handle bulk or many records at a time. This is also true for asynchronous Apex methods (those annotated with the @future keyword). The differences between synchronous and asynchronous Apex can be found

    9) Avoid Hardcoding IDs
    When deploying Apex code between sandbox and production environments, or installing Force.com AppExchange packages, it is essential to avoid hardcoding IDs in the Apex code. By doing so, if the record IDs change between environments, the logic can dynamically identify the proper data to operate against and not fail.

    Hope this helps.

    #35128
    Salesforce | Parul Parul #2
    Forcetalks

    Best Practice:

    #1: Bulkify your Code

    #2: Avoid SOQL Queries or DML statements inside FOR Loops

    #3: Bulkify your Helper Methods

    #4: Using Collections, Streamlining Queries, and Efficient For Loops

    #5: Streamlining Multiple Triggers on the Same Object

    #6: Querying Large Data Sets

    #7: Use of the Limits Apex Methods to Avoid Hitting Governor Limits

    #8: Use @future Appropriately

     

    Thanks

    #36018
     Prachi #9
    Forcetalks

    hi,

    There should only be one trigger for each object.
    Avoid complex logic in triggers. To simplify testing and resuse, triggers should delegate to Apex classes which contain the actual execution logic.
    Bulkify any “helper” classes and/or methods.
    Trigers should be “bulkified” and be able to process up to 200 records for each call.
    Execute DML statements using collections instead of individual records per DML statement.
    Use Collections in SOQL “WHERE” clauses to retrieve all records back in single query
    Use a consistent naming convention including the object name (e.g., AccountTrigger)

    thanks.

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

Please to reply to this topic.

CONTACT US

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

Sending

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 2018 Forcetalks. All Right Reserved.

Log in with your credentials

or    

Forgot your details?