Loading
The online Trailblazer Community becomes read-only Oct 30, 2026Read More
Important Advisory: iOS Update Impacting CG Mobile ApplicationRead More
Extend Salesforce with Clicks, Not Code
Dynamic Interactions Limits and Limitations

You are here:

  1. Salesforce Help
  2. Docs
  3. Extend Salesforce with Clicks, Not Code

Dynamic Interactions Limits and Limitations

Keep these considerations in mind when working with Dynamic Interactions in the Lightning App Builder.

Required Editions

Available in: Lightning Experience

Available in: Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions
  • Dynamic Interactions is supported only on app pages.
  • Only LWC custom components can be source components, but any component present on the page (Aura or LWC) can be a target.
  • Dynamic Interactions isn’t supported on pages based on custom page templates.
  • Only String and Rich Text type properties can use expressions to define their values.
  • The “required” property restriction isn’t respected when defining a new value for a target property in Dynamic Interactions, regardless of its type or whether it’s defined with an expression.
  • Event is the only context supported for expressions in interactions.
  • You can use expressions only for properties of type String, Integer, and Boolean.
  • You can’t set a target property value as an array or list of values, such as a multi-select picklist.
  • You can set a target property value of a String attribute to empty using Metadata API but not in the Lightning App Builder UI.
  • Dynamic Interactions doesn’t work in the Mobile Only app in the Salesforce mobile app or in the legacy tablet mobile experience.
  • When a dependent property is autopopulated with a value based on a selection you made or a value you entered in another property, the autopopulated value isn’t saved unless you “touch” the dependent property field by clicking into it or tabbing to it.
 
Loading
Salesforce Help | Article