top of page
  • Writer's pictureAvi Rai

Dynamic Interaction in two Lightning web components

What are dynamic interactions?

Dynamic Interactions is one more step to make Lightning pages more dynamic and interactive. With Dynamic Interactions, an event occurring in one component on a Lightning page, such as the user clicking an item in a list view, can update other components on the page.

They let admins create applications with components that communicate and transform based on user interactions, all in the Lightning App Builder UI. It unlocks capabilities that previously were reserved only for developers.

Dynamic Interactions has four major building blocks.

  • Event—Anything that can trigger an interaction, such as a mouse click, a button press, or a change in a field’s value.

  • Interaction—An activity that happens between the source and the target.

  • Source—The item triggering the event. Currently, only custom Lightning web components and the Dynamic Actions Bar component (Pilot) are supported as sources.

  • Target—The item that’s the target of the interaction. Any component on a Lightning page can be a target.

To expose an event from the component, you need to define the event and its schema in the meta XML file.

event - Exposes the event for Dynamic Interactions and makes it available for the component in the Lightning App Builder. The event subtag supports the name, label, and description attributes.

name—The name of the event as defined in the component’s .js file. If no label attribute is defined, the name value is shown in the list of available events for the component in the Lightning App Builder.

label—The admin-friendly label for the event.

description—The description of the event, which displays in an i-bubble on the event label in the Lightning App Builder.

schema - Provides the shape of the event. Content in the schema subtag must be in JSON format.

Our use case - There are two independent custom Lightning web components. The first one(AccountList) contains the list of accounts and the other one(AccountDetail) displays account record detail using the record view form. We have placed these two components on an app page. We want that whenever an account is selected from the list, its detail should be displayed by the AccountDetail component. We will accomplish this by using Dynamic Interactions.

1. Create the AccountList component(source) that displays the list of accounts.

a. The HTML file - Display the list of accounts.

	<template for:each={accounts} for:item="account">
		<div key={account.Id} onclick={handleClick} data-id={account.Id} class="slds-box slds-var-p-around_small"
			<p class="slds-truncate" title={account.Name}>{account.Name}</p>
			<p class="slds-truncate" title={account.Industry}>{account.Industry}</p>

b. The js file- Trigger custom event whenever an account is selected.

import { LightningElement,wire,track } from "lwc";
import getAccounts from '@salesforce/apex/AccountController.getAccounts';

export default class TestDynamicInteraction extends LightningElement {
    @track accounts = [];

    wireAccounts ({error, data}) {
        if (error) {
        } else if (data) {
            this.accounts = data;

	handleClick(event) {
		let recordId =;
			new CustomEvent("itemselected", {
				detail: {
					recordId: recordId

c. The meta XML file - Exposes the event.

<?xml version="1.0" encoding="UTF-8"?>
<LightningComponentBundle xmlns="">
    <masterLabel>Account List</masterLabel>
        <targetConfig targets="lightning__AppPage">
            <event name="itemselected" label="Item Selected" description="This event fires when an item is selected.">
                        "type": "object",
                        "properties": {
                            "recordId": {
                                "type": "string",
                                "title": "Record ID",
                                "description": "Enter an 18-digit record ID."
    <description>Defines an event for an Account List component</description>

2. Create the AccountDetail component(Target) that displays the account record's detail.

a. The HTML file - Shows account record using record view form.

	<lightning-card title="Selected Account Details">
		<lightning-record-view-form object-api-name="Account" record-id={accountId}>
			<div class="slds-var-p-left_small">
				<lightning-output-field field-name="Name"> </lightning-output-field>
				<lightning-output-field field-name="Industry"> </lightning-output-field>
				<lightning-output-field field-name="Active__c"> </lightning-output-field>
				<lightning-output-field field-name="Type"> </lightning-output-field>

b. The js file - Use the event property.

import {api, LightningElement } from "lwc";

export default class Test extends LightningElement {

	@api get recordId() {
		return this.accountId;    
	set recordId(value) {
		if (value) {

c. The meta XML file - Make the property available in the Lightning Builder UI

<?xml version="1.0" encoding="UTF-8" ?>
<LightningComponentBundle xmlns="">
    <masterLabel>Account Detail</masterLabel>
        <targetConfig targets="lightning__AppPage">
            <property name="recordId" type="String" />

3. After creating both components, you will need to place them on the App page and establish interaction between them.

Well, that's it! You can now try seeing your interaction live. Quite an easy right.

References -

Thanks for reading. Welcome all your thoughts on this. Stay safe and happy :)

983 views0 comments

Recent Posts

See All

What is Modal? A modal overlays a popup on top of the current app window. This paradigm is used in cases such as the creation or editing of a record, as well as various types of messaging and wizards.

What are Platform Events? Platform events are the event messages (or notifications) that your apps send and receive to take further action. They simplify the process of communicating changes and respo

Hello everyone, We know that there are two methods to call an Apex method from a Lightning Web Component: Wire Apex Methods to Lightning Web Components Call Apex Methods Imperatively When calling apex

Post: Blog2_Post
bottom of page