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...
To implement dynamic search functionality in a Lightning Web Component (LWC) in Salesforce, you can follow the steps below: 1. Create the HTML Markup: Start by creating the HTML markup for your LWC component. Include an input field where users can enter their search criteria, and a list to display the search results dynamically. <template> <lightning-input type="text" label="Search" onchange={handleSearch}></lightning-input> <ul> <template for:each={searchResults} for:item="result"> <li key={result.Id}>{result.Name}</li> </template> </ul> </template>