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: Blockchain technology has gained significant attention in recent years for its ability to provide secure and transparent transactions. Salesforce, a leader in cloud-based CRM solutions, has introduced Salesforce Blockchain to extend these benefits to its customers. In this blog post, we will explore the features, benefits, and potential of Salesforce Blockchain in revolutionizing trust and transparency in business transactions. 1. Understanding Salesforce Blockchain: Salesforce Blockchain is a decentralized and distributed ledger technology that enables multiple parties to securely and transparently share and verify data. Built on the trusted Salesforce platform, it provides a trusted environment for businesses to collaborate and conduct transactions with enhanced security and immutability. 2. Enhancing Trust and Transparency: Salesforce Blockchain facilitates trust and transparency by providing a single, shared view of data among multiple participants. Each transa...