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 today's digital era, managing customer relationships and sales processes efficiently is crucial for any business. Salesforce, the leading customer relationship management (CRM) platform, offers a wide range of features and functionalities to streamline sales operations. In this blog post, we will explore three fundamental concepts in Salesforce: Profiles, Permission Sets, and Roles. Understanding these concepts is essential for effectively managing user access and security within the Salesforce ecosystem. 1. Salesforce Profile: A Salesforce profile is a collection of settings and permissions that determine what a user can do within the CRM system. Each user in Salesforce is assigned a profile, which controls their access to standard and custom objects, fields, tabs, and various other features. Profiles define the baseline level of access and functionality for users. Some common Salesforce profiles include System Administrator, Standard User, Marketing User, and...