New Lightning Components: Salesforce Dynamic Interactions

Share this article...

There’s a new player in the “dynamic” family: alongside Dynamic Forms and Dynamic Actions we are excited to introduce Dynamic Interactions!

Dynamic Interactions is part of a larger trend in digital transformation to provide new low code solutions that empower non-code app builders (that’s Salesforce Admins to you and I) to create interactive, responsive experiences using drag and drop tools.

Features such as Dynamic Interactions will enable companies to push forward, faster than ever, pivoting to respond to the changing demands of users and customers, without the delay of waiting for developer resources.

What are Dynamic Interactions?

Dynamic Interactions are interactive components such as a list, a data entry form, a chart or a map. Whilst the initial component is created by a developer, it can then be added to Salesforce layouts by the Administrator who can control how the component interacts with other components on the page and what action it should take. These components are reusable, so they only need to be created once, and can then be used repeatedly.

Previously, to achieve similar functionality, developers had to build a new component every time and program their actions; this meant relying on developer resource which, for many businesses, slowed down the pace of development. Dynamic Interactions will drastically improve development cycles, as well as reduce the costs associated with developing the Salesforce platform.

So, what do Dynamic Interactions look like in practice?

As part of their announcement, Salesforce uses Yelp as an example. Yelp has used Dynamic Interactions to add an interactive map; when a user selects a particular company from a list, that company’s location is automatically highlighted in the embedded map.

Dynamic Interactions is expected to be generally available in Winter ’22.

4 thoughts on “New Lightning Components: Salesforce Dynamic Interactions

    1. Christine Marshall


      Hi Yi,

      Looks like there was a typo in the original Salesforce article – we have now updated our post to reflect the change.

      Best, Christine

Add Comment