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...
Here's an example of a record form with field validation using code in Lightning Web Components (LWC) in Salesforce: recordFormExample: <template> <lightning-card title="New Record Form" icon-name="standard:account"> <div class="slds-p-around_medium"> <lightning-record-edit-form object-api-name="Account" onsubmit={handleSubmit}> <lightning-messages></lightning-messages> <div class="slds-grid slds-wrap"> <div class="slds-col slds-size_1-of-2"> <lightning-input-field field-name="Name" required></lightning-input-field> ...