---
schema_version: "1"
id: f8bccbc9f9667926cbc1d332cd9900dafe41e0af1eef092fc94f658c146d90c5
title: Expressions in Dynamic Interactions Target Properties
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/dynamic_interactions_expressions.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.dynamic_interactions_expressions.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5cd1c6b367cc2e79211b56ad8fba628e69f1a12ad703daffd10852836ea45215
description: "An expression is a small chunk of code that can be evaluated to a value. It can be as literal and simple as 1+1 or a more complex combination of variables, operators, and functions. One expression is supported for Dynamic Interactions in the Lightning App Builder: {!Event.eventPropertyName}. You can use this expression when setting target component property values in the Lightning App Builder UI and in Metadata API. The value of the eventPropertyName part of the expression varies based on which properties the developer makes available for the event in the source component."
products:
  - Salesforce Platform
  - Security
release: "264"
---
# Expressions in Dynamic Interactions Target Properties

An expression is a small chunk of code that can be evaluated to a value. It can be as literal and simple as `1+1` or a more complex combination of variables, operators, and functions. One expression is supported for Dynamic Interactions in the Lightning App Builder: `{!Event.eventPropertyName}`. You can use this expression when setting target component property values in the Lightning App Builder UI and in Metadata API. The value of the `eventPropertyName` part of the expression varies based on which properties the developer makes available for the event in the source component.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col>
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p style="margin-bottom:0;">Available in: <strong>Group</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>,
              <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong>
              Editions
            </p>
          </td>

        </tr>
      </tbody>
    </table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_note.png)

Note If you see the ![Expression button icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/extend_click/images/di_expression_icon.png) button on a target property, you can set its value with an expression.

With an expression, you can pass a value, such as a record ID or an API name, to the target item. Then when the event fires, the target item can use that value. Using an expression to define a property value makes the event interaction dynamic. We can illustrate this with an example of an app page with custom Account List and Account Location components. Here, an admin is configuring an interaction between the Account List source component and the Account Location target component.

![Interaction details pane with an empty Account Location property](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/extend_click/images/di_example_expression1.png)

The goal for the interaction in this example is that when a user clicks an account in the list, the Account Location component updates to show the selected account’s location as a point on a map. But the Account Location component needs to know the record ID of the selected account to do that. Passing the record ID into the Account Location component tells the component which record to look at to pull the address information. In this case, the developer made the `recId` property available as part of the event, so the target value can be set to the active list item’s record ID using the `{!Event.recId}` expression.

![Account Location property filled with an expression](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/extend_click/images/di_example_expression2.png)

Why not enter a 15- or 18-digit record ID into the field? If you do, any item clicked in the Account List always resolves to that one record ID, which isn’t dynamic and is incorrect.

If the developer makes more than one target property available, you can set the property to be passed in by starting to type the expression in the field. After the period, you can use autocomplete to select which property to use in the expression. But don’t forget to add the ending bracket `}` after you make your selection.

![Property field expression autocomplete](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/extend_click/images/di_example_expression3.png)

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_note.png)

Note Expression autocomplete doesn’t work when:

- Using expressions in the rich text editor
- Typing an expression in a text field without first clicking the expression button (![Expression button icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/extend_click/images/di_expression_icon.png))

#### See Also

- [Configure Interactions in the Lightning App Builder](https://help.salesforce.com/s/articleView?id=platform.dynamic_interactions_configure.htm&release=264.0.0&type=5 "After you have a custom source component with exposed events in your org, you can assign event targets and configure the event interactions in the Lightning App Builder.")
- [Dynamic Interactions Limits and Limitations](https://help.salesforce.com/s/articleView?id=platform.dynamic_interactions_limitations.htm&release=264.0.0&type=5 "Keep these considerations in mind when working with Dynamic Interactions in the Lightning App Builder.")
- [Dynamic Interactions in the Lightning App Builder](https://help.salesforce.com/s/articleView?id=platform.dynamic_interactions_overview.htm&release=264.0.0&type=5 "Dynamic Interactions is part of our continuing drive 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. Dynamic Interactions lets 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.")