Custom Metadata Types vs Custom Settings vs Custom Labels 💬 In plain words: Three lookalikes: Custom Metadata = configuration that DEPLOYS with your code (best for app settings). Custom Settings = org/user-specific values, changeable at runtime (hierarchy type is great for bypass switches). Custom Labels = translatable text for the UI. 📌 Example: API endpoint URLs per environment → Custom Metadata (deploys with code, sandbox vs prod values). A 'Bypass_Automation__c' checkbox an admin flips during data load → hierarchy Custom Setting. The word 'Submit' translated to Hindi → Custom Label. 🎬 Real-Life Example: The Fee Table Trapped Inside Code Skyline charges a different delivery fee per city. Apex needs those rates on every booking. The Old/Bad Way: if (city == 'Delhi') fee = 50. Else if (city == 'Mumbai') fee = 65. … Every rate change is a code change, a test run, and a deployment. Why this is bad: Business data is trappe...
Introduction:
In the world of Salesforce development, triggers play a vital role in automating business processes and enhancing the platform's capabilities. As a Salesforce professional or aspiring developer, it's crucial to be well-prepared for scenario-based interview questions related to triggers. In this blog post, we will explore common scenarios and provide valuable insights on how to tackle them effectively during interviews.
1. Scenario: Updating Related Records
Description: You are required to write a trigger that updates a custom field on an object's related records whenever a specific field is modified on the object itself.
Solution:
To accomplish this, you can utilize an after trigger on the object. Retrieve the related records using a SOQL query and update the desired field accordingly. Make sure to consider bulkification to handle multiple records efficiently.
2. Scenario: Preventing Record Deletion
Description: Write a trigger that prevents a user from deleting a record if it meets specific criteria.
Solution:
In this scenario, an example of a before delete trigger can be used to perform validation on the records before deletion. If the record meets the specified criteria, throw an exception or add an error message to prevent deletion. This ensures data integrity and compliance with business rules.
3. Scenario: Roll-up Summary Calculations
Description: Implement a trigger that performs roll-up summary calculations on a parent object whenever child records are inserted, updated, or deleted.
Solution:
To achieve this, use an after trigger on the child object and perform the necessary calculations using SOQL queries and aggregation functions. Update the corresponding fields on the parent object with the calculated values. Consider handling bulk operations efficiently to minimize governor limits.
4. Scenario: Field Validation
Description: Develop a trigger that enforces specific field validation rules when records are being created or updated.
Solution:
In this case, you can use a before trigger to validate the field values before they are saved. Implement the required validation logic within the trigger, checking for conditions and raising exceptions or adding error messages when the validation rules are not met. This ensures data integrity and maintains the quality of information within the Salesforce system.
5. Scenario: Cross-Object Updates
Description: Write a trigger that updates fields on related objects when a specific field is modified on a particular object.
Solution:
To accomplish this, utilize an after trigger on the object that needs to be monitored for changes. Query the related objects using SOQL, update the desired fields based on the changes, and perform DML operations to save the updates. Make sure to handle bulk operations efficiently to avoid hitting governor limits.
Conclusion:
Mastering scenario-based interview questions for Salesforce triggers is essential for demonstrating your expertise in Salesforce development. By understanding these common scenarios and their respective solutions, you can showcase your ability to create efficient and effective triggers that automate business processes and maintain data integrity. Remember to emphasize best practices such as bulkification, governor limit considerations, and maintaining clean code structure during your interviews. Good luck!