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...
Exploring Lightning Data Service: A Comprehensive Guide with 10 Code Examples and Detailed Explanations
Lightning Data Service (LDS) is a powerful tool in Salesforce Lightning that allows you to work with Salesforce data without writing complex Apex code. It provides a standard way to access, create, update, and delete records in the database. Here are ten code examples that demonstrate the usage of Lightning Data Service: 1. Retrieve a single record by ID: import { LightningElement, wire } from 'lwc'; import { getRecord } from 'lightning/uiRecordApi'; export default class ExampleComponent extends LightningElement { recordId; @wire(getRecord, { recordId: '$recordId', fields: ['Account.Name'] }) account; handleRecordIdChange(event) { this.recordId = event.target.value; } }