Salesforce is a great tool for building out custom solutions to meet your organization’s unique needs. You have tremendous flexibility in building out a data model and user interface (UI) that captures all of the complexity of your specific user workflows using our low-code tools. This flexibility can sometimes come at a cost, however. Over time, your pages can become more and more complex, reducing usability and presenting barriers to adoption. Our customers have told us that their users can end up being overwhelmed with the number of fields or components on a page, especially when some fields may not be relevant to them at a specific point in a process.
Dynamic Forms can help. With Dynamic Forms, you can tailor layouts based on record data, user details, and device type—giving you more granular control over what your end users see on a Record page at a given point in time. This has been one of our most requested IdeaExchange items, and it was made generally available (GA) for standard objects and mobile devices as of the Winter ’24 Release. In this post, we’ll walk through three examples of how you can use Dynamic Forms to provide a more tailored end-user experience and drive increased productivity for your end users.
For our first example, I’m going to talk about the ability to enable field and field section visibility based on device type. A number of our customers have indicated that they’d like to provide a slimmed-down layout with a reduced set of fields for their users on mobile, and some of our customers have even built custom components to make this possible.
With Dynamic Forms on Mobile, building custom components is no longer necessary! You can now create dynamic layouts that are specifically for the mobile form factor, and manage the fields that show up from directly within Lightning App Builder; no code required.
Let’s take a look at how we can do this. First, we’re going to enable Dynamic Forms on Mobile from the Salesforce Mobile App section in the Setup menu.
Now, let’s take a look at the Asset object, one of the newly-enabled entities as of the Winter ’24 Release. When we open the Lightning Record page for this object in Lightning App Builder, we can click the Record Detail component in the canvas, and follow the prompt in the property panel on the right-hand side to convert this component to Dynamic Forms.
The existing layout is carried over, so we don’t need to redo that configuration.
We can now start to add visibility rules based on device type. For this object, field sales reps might not need to see all of the technical details while they’re out in the field. We can configure the page so that the Service Information details only show up when a user is at their desk.
When we open this on mobile, we see the slimmed-down layout, which no longer shows the Service Information section.
This is simple but powerful, as a view that’s more tailored to an end user’s specific needs can help drive mobile adoption.
Prior to Dynamic Forms, if there was even a minor variation in what two different users needed to see, you would have had to create different page layouts for those different users. That’s no longer necessary! With Dynamic Forms, if it’s only a specific field or section that differs from one profile to another, you can set conditional visibility on these fields or sections instead, leaving the majority of the page the same.
Let’s take a look at how to set this up. In our example with the Asset object, there might be some fields that are only relevant to Sales. In this case, we can click Advanced under the Filter Type and choose to filter on aspects of the user’s Profile.
Setting conditional visibility based on user details, such as Profile, can reduce administrative complexity by reducing the number of page layouts and/or Lightning Record pages you need to manage.
Lastly, I’m going to cover one of the use cases that a number of our customers discussed with us during the Dynamic Forms on Mobile pilot: showing and hiding sections based on the step a record is on within a process.
For the Asset use case, end users might like to see different field sections throughout the product lifecycle; for example, a different set of fields is going to be relevant after a product has been installed versus when it was initially purchased and still hasn’t shipped. Prior to installation, we need to track the shipping date and schedule installation date and time; these fields are not as relevant after installation.
To meet this requirement, we can add field section visibility on our Shipping Information section, so that it doesn’t show up until the status is set to Purchased.
Similarly, the availability information won’t be relevant until the Asset has been installed.
This is a simple example, but the principle can be extended to more powerful use cases as well. By allowing dynamic changes to pages throughout a process, you can ensure your end users always have the most relevant information (and nothing more) in front of them.
So, how can you get started? Dynamic Forms was enabled for all Lightning Web Components (LWC)-enabled standard objects and mobile as of the Winter ’24 Release. You can try it out in the playground on Trailhead, and get started in your Salesforce org today.
As always, we’d love your feedback on the feature. Join the discussion in our Trailblazer Community Group focused on Dynamic Forms, Actions, Lists and More!
True to the Core is a favorite session at Dreamforce and TDX, especially for admins who want an opportunity to connect with Salesforce executives and product managers on the topics that are most important to you. True to the Core offers an unfiltered look into our product development plans, and gives you the chance to […]
Winter ’25 is almost here! Learn more about Conditional Field Formatting and check out Be Release Ready to discover more resources to help you prepare for Winter ’25. The challenge with configuring visual indicators today Creating custom visual indicators to call attention to key fields is a common Salesforce configuration requirement. Visual indicators make it […]
Gosh, it just seemed like yesterday that I was putting together my blog post about Summer. But here we are, getting ready for Winter ’25. I find it a bit comforting to think about snow as a way to cool down in this 80/90 degree weather we’ve been having in Boston. Mochi (my Pomeranian) would […]
