Skip to main content

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

Embedding a Visualforce Page in LWC & Two-Way Communication: LWC Example Codes

Introduction:

In this blog post, we will explore how to embed a Visualforce page in a Lightning Web Component (LWC) and establish two-way communication between them. Visualforce pages provide powerful capabilities for building custom UIs, while LWC offers a modern and efficient framework for building Lightning Experience components. By combining the two, you can leverage the best of both worlds. We will provide example codes to illustrate the process and demonstrate how to achieve seamless integration between Visualforce pages and LWCs.


Prerequisites:


To follow along with this tutorial, you should have a basic understanding of Lightning Web Components and Visualforce. Familiarity with JavaScript, HTML, and Apex will also be helpful.


Step 1: Setting up the Visualforce Page


To begin, create a Visualforce page that will be embedded in the LWC. This page can contain any desired functionality and UI elements. Here's an example of a simple Visualforce page:


<apex:page>

  <h1>Hello Visualforce!</h1>

  <p>This is a Visualforce page.</p>

</apex:page>


Step 2: Creating the LWC Component


Next, let's create the Lightning Web Component that will host the Visualforce page. Here's a basic structure for the LWC:


<template>

  <div>

    <!-- Placeholder for the Visualforce page -->

    <div class="vfPageContainer"></div>

  </div>

</template>


import { LightningElement } from 'lwc';


export default class EmbeddedVFPage extends LightningElement {

  renderedCallback() {

    // Load the Visualforce page in the container element

    this.loadVFPage();

  }


  loadVFPage() {

    const container = this.template.querySelector('.vfPageContainer');


    // Create an iframe and set the source to the Visualforce page URL

    const iframe = document.createElement('iframe');

    iframe.src = '/apex/YourVisualforcePage';

    iframe.width = '100%';

    iframe.height = '100%';


    // Append the iframe to the container element

    container.appendChild(iframe);

  }

}


Step 3: Establishing Two-Way Communication


To enable two-way communication between the LWC and the embedded Visualforce page, we can utilize the postMessage API. This API allows sending messages between different windows or frames. Here's how you can implement it:


Inside the Visualforce page:


<script>

  // Receive messages from the parent window (LWC)

  window.addEventListener('message', event => {

    const message = event.data;


    // Process the received message

    // ...

  });


  // Send a message to the parent window (LWC)

  const sendMessageToParent = (message) => {

    window.parent.postMessage(message, '*');

  };

</script>


Inside the LWC component:


loadVFPage() {


  // Attach a message event listener to the iframe

  iframe.addEventListener('message', event => {

    const message = event.data;


    // Process the received message

    // ...

  });


  // Send a message to the embedded Visualforce page

  const sendMessageToVFPage = (message) => {

    iframe.contentWindow.postMessage(message, '*');

  };

}


Conclusion:


In this blog post, we learned how to embed a Visualforce page within a Lightning Web Component (LWC) and establish two-way communication between them. By combining the power of Visualforce pages with the flexibility of LWCs, you can create rich and interactive user interfaces that leverage the strengths of both technologies. The provided example codes should serve as a starting point for your own implementations, allowing you to build seamless integrations between Visualforce pages and LWCs. Experiment with different functionalities and explore the possibilities of this powerful combination.


Remember to refer to the official Salesforce documentation for more detailed information and additional features.


Happy coding!

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.