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 the world of Salesforce development, efficient search functionality is crucial for retrieving relevant data. One powerful tool in the Salesforce developer's arsenal is the Salesforce Object Search Language (SOSL). SOSL allows developers to perform text-based searches across multiple objects, providing a streamlined way to find and display the information users need. In this blog post, we will explore how to use SOSL within the Lightning Aura framework, accompanied by practical code examples. What is SOSL? Salesforce Object Search Language ( SOSL ) is a Salesforce-specific language used for searching multiple objects simultaneously. Unlike Salesforce Object Query Language ( SOQL ), which retrieves specific records from a single object, SOSL enables you to search across multiple objects based on a text search term. SOSL returns a list of records that match the search criteria, making it an excellent choice for scenarios where you need to query data across different o...