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 Salesforce development, working with JSON information is a not unusual challenge when integrating with external systems or handling facts in a bendy and dynamic way. Salesforce affords a powerful approach called JSON.DeserializeUntyped that permits developers to parse JSON strings right into a extra potential format. In this weblog submit, we'll discover the bits and bobs of 'J SON.DeserializeUntyped ' in Apex, understand its utilization, and offer sensible code examples to demonstrate its abilties.