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...
Reports, Dashboards & Analytics Architecture 💬 In plain words: Reports are questions you ask of your data; report types decide which objects a report is even allowed to ask about; dashboards show many answers on one screen. Key trap: who a dashboard 'runs as' decides whose data everyone sees. 📌 Example: The VP's dashboard shows 40 deals; a rep opens the same dashboard and sees 12. Check 'view dashboard as': it runs as the viewer, and the rep's sharing only reaches 12 opportunities. Same report, different eyes. Concept Reporting starts with Report Types. A report type decides which objects and fields are reportable, and whether the join is inner or outer, that is the 'with or without related records' choice. It is the most under-appreciated lever on the platform. Custom report types unlock cross-object paths and relationships that are otherwise hidden. Reporting snapshots capture data at a point in time into a custom object, whic...