Best Practices of Apex In Salesforce

Please follow these Salesforce Best Practices to improve our code Quality, Readability, and Reusability. Also, you can use Salesforce Best Practices to optimize our code.

1. Avoid DML/SOQL/SOSL statements in loops : 

• Do not place SOQL or DML(insert/update/delete/undelete) statements inside a loop
• When these operations are placed inside a for loop, database operations are invoked once per iteration of the loop making it very easy to reach these SFDC governor limits.
• Solution: Move SOQL/DML out of loops
• Query: If you need query results, get all the records using a single query and iterate over the resultset
• Update: If you need to update, batch up the data into a collection and invoke DML once for that collection

2. Bulkify your Code
3. Using Collections, Streamlining Queries, and Efficient For Loops
4. Querying Large Data Sets
5. Use of the Limits Apex Methods to Avoid Hitting Governor Limits
6. Use @future Appropriately
7. Writing Test Methods to Verify Large Datasets
8. Avoid Hardcoding IDs : 

• Make sure that the helper methods are properly designed to handle bulk records
• These methods should be written to be invoked with a set of records, especially if the technique has a SOQL query or DML operation
• Use the power of the SOQL where clause to query all data needed in a single query

public static void hardCodeIdExample() { 
        if (opp.RecordTypeId == '016500000005WAr') {
            //do some logic here.....
        } else if (opp.RecordTypeId == '016500000008WAr') {
            //do some logic here for a different record type...
        }
   }

If you run the above code in different environments, it will fail. Then Please use this code snippet:

public static void hardCodeIdExample() {
        if (opp.RecordTypeId ==           Schema.sObjectType.Opportunity.getRecordTypeInfosByName().get('Test') ) {
            //do some logic here.....
        } else if (opp.RecordTypeId == Schema.sObjectType.Opportunity.getRecordTypeInfosByName().get('TestData’')) {
            //do some logic here for a different record type...
        }
}

9. Bulkify your Helper Method :

• Make sure that the helper methods are correctly designed to handle bulk records
• These methods should be written to be invoked with a set of records, especially if the technique has a SOQL query or DML operation
• Use the power of the SOQL where clause to query all data needed in a single query

10. Use only one trigger per SObject Type. 
11. Avoid logic in the trigger
12. Apex unit test should not use SeeAllData True
13. Naming conventions : 

• Apex Class naming convention (Pascal case)

E.g. :  public class DataClass { }

• Method naming conventions (Camel  Case)

E.g. : public void testMethod() { }

• Field or local variable naming conventions (Camel Case)

E.g. : Integer instanceField;

For More Salesforce Naming Conventions refer to this link: Salesforce Naming Conventions

15. Increase readability by indenting code and breaking up long lines.
16. Avoid nesting loops within loops.
17. Write comments with a good balance between quality and quantity (explain, but don’t over-explain). Always provide documentation comments (method and class headers). Provide inline comments only when necessary to clarify complex code.
18. Break methods into multiple smaller methods if possible, making your code more modular and easier to read and maintain.
19. Make reusability of Apex Code
20. Code coverage
    • Bulk Records
    • Positive & Negative testing.
    • Restricted User testing.
    • One Assert Statement per method
    • should not use @isTest(seeAllData=true)
21. Use Database Methods while doing DML operation
22. Test Multiple Scenarios

Note: If you are using Visual Studio Code as your IDE, consider using the Apex PMD extension (included in the Resources section) to automatically check your code for best practices.

Conclusion