Skip to main content

Posts

Showing posts with the label Debug Mode

Latest Post

Custom Metadata Types vs Custom Settings vs Custom Labels

  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...

LWC Debugging Tools: A Guide to the Best Tools for Troubleshooting Your Components

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.

Enabling Debug Mode for LWC - A Comprehensive Guide

Introduction: Lightning Web Components (LWC) is a modern framework for building dynamic web applications on the Salesforce platform. While developing LWC components, it is essential to have robust debugging capabilities to identify and fix issues efficiently. In this blog post, we will explore how to enable debug mode for LWC and leverage its powerful features to streamline your development process.

Execution Modes for LWC: Understanding the Different Modes

  Lightning Components are a powerful way to build custom user interfaces for Salesforce applications. However, there are different execution modes for Lightning Components, and it's important to understand the differences between them so that you can choose the right mode for your needs. In this blog post, we'll discuss the two main execution modes for Lightning Components: debug mode and production mode. We'll also cover some of the pros and cons of each mode, so that you can make an informed decision about which mode to use for your components. Debug Mode Debug mode is the default execution mode for Lightning Components. It's designed to make it easier to debug your components by providing more detailed error messages and logging output. In debug mode, the JavaScript source code for your components is not minified, which makes it easier to read and understand.

Popular Posts

Salesforce LWC Code for Multi-Select Lookup

Introduction: In Salesforce Lightning Web Components (LWC), implementing a multi-select lookup field can enhance the user experience and provide greater flexibility for selecting multiple related records. In this blog post, we will walk through the process of creating a multi-select lookup field using LWC. We will cover the required code snippets and provide step-by-step instructions to help you implement this functionality in your Salesforce org.