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:
Lightning Web Components (LWC) are a powerful way to build custom user interfaces in Salesforce. However, as with any programming language, there can be times when things go wrong. That's where debugging tools come in.
In this blog post, we'll take a look at some of the best LWC debugging tools available. We'll cover both browser-based tools and Salesforce-specific tools, so you'll have everything you need to troubleshoot your components.
Browser-based tools:
- Chrome DevTools: Chrome DevTools is a comprehensive suite of debugging tools that can be used to debug any web application, including LWC components. With Chrome DevTools, you can inspect the HTML, CSS, and JavaScript of your components, set breakpoints, and step through the code line by line.
- Firebug: Firebug is a popular Firefox extension that also provides a variety of debugging tools for web applications. Firebug is similar to Chrome DevTools, but it offers some additional features, such as the ability to debug AJAX requests.
- The Lightning Web Components Inspector: The Lightning Web Components Inspector is a Salesforce-specific tool that can be used to debug LWC components. The Lightning Web Components Inspector provides a graphical interface for inspecting the properties and state of your components, as well as the ability to trace the execution of your code.
Salesforce-specific tools:
- Debug Mode: Debug Mode is a Salesforce feature that can be enabled to make it easier to debug JavaScript code. When Debug Mode is enabled, Salesforce will not minify or obfuscate your JavaScript code, which makes it easier to read and debug.
- Log Inspector: The Log Inspector is a Salesforce tool that can be used to view the logs of your Salesforce org. The Log Inspector can be helpful for debugging LWC components, as it can show you any errors that occur when your components are executed.
Conclusion:
These are just a few of the best LWC debugging tools available. With the right tools, you can quickly and easily troubleshoot any problems you encounter with your components.
I hope this helps!