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...
We have the standard history for our fields in salesforce. We can use that functionality from the related list. Here we will see that functionality using component and apex class. This will be a generic code for custom objects. Just paste the id of the record for which you want to see history. Make sure you have enabled history tracking for that object. Here is the apex class for JSON. Save this first. HistoryWrapper.cls public class HistoryWrapper{ public WrapperClass_attributes attributes; public String CreatedById; public datetime CreatedDate; public String Field; public boolean IsDeleted; public string NewValue; public string OldValue; public String Id; public Wrapperclass_CreatedBy CreatedBy; public static list<HistoryWrapper> parse(String json){ ret...