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 f...