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: Data security is of paramount importance in today's digital landscape, and Salesforce takes the protection of customer data seriously. With a robust and comprehensive security framework, Salesforce ensures that sensitive information stored in its cloud-based CRM platform remains secure from unauthorized access, breaches, and data loss. In this blog post, we will explore the key security measures implemented by Salesforce to safeguard your data. 1. Data Encryption: Salesforce employs industry-standard encryption techniques to protect data both at rest and in transit. Data at rest, stored in databases and storage systems, is encrypted to prevent unauthorized access in case of physical or infrastructure compromise. Data in transit, when transmitted over networks, is encrypted using secure protocols such as Transport Layer Security (TLS) to prevent interception and tampering. 2. User Authentication and Access Control: Salesforce implements robust user authenticatio...