Skip to main content

Posts

Showing posts with the label Pub-Sub Pattern

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

Leveraging the Power of Salesforce LWC Pub-Sub Pattern with Lightning Message Service

Introduction: Salesforce Lightning Web Components (LWC) and Lightning Message Service provide developers with a powerful combination to implement the publish-subscribe (pub-sub) pattern within the Salesforce platform. This pattern allows components to communicate and exchange data efficiently, enabling seamless coordination and collaboration between different parts of an application. In this blog post, we will explore the concept of the pub-sub pattern and delve into how to leverage Lightning Message Service to implement it in Salesforce LWC. 1. Understanding the Publish-Subscribe Pattern: The publish-subscribe pattern is a messaging paradigm where components or modules can act as publishers or subscribers. Publishers send messages (events) containing data, while subscribers listen for specific events and respond accordingly. This decoupled approach enables loose coupling between components and promotes reusability, scalability, and flexibility in application design. 2. Introduci...

Enhancing Salesforce Lightning Web Components (LWC) with Effective Component Communication

Introduction: Salesforce Lightning Web Components (LWC) provide a powerful framework for building modern, dynamic user interfaces within the Salesforce platform. One of the key aspects of developing robust LWC applications is efficient component communication. In this blog post, we will explore various techniques and best practices for effectively communicating between LWC components, enabling seamless data sharing and collaboration. 1. Parent-to-Child Component Communication: One common scenario in LWC development is passing data from a parent component to a child component. This can be achieved by leveraging properties or attributes. The parent component sets the values of properties or attributes, which are then accessed by the child component. This approach enables data sharing and ensures that child components have access to the necessary data for rendering. 2. Child-to-Parent Component Communication: Conversely, there are situations where a child component needs to communi...

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.