The premise of Dynamic Forms is to create user centric, intuitive page layouts that display information at the right time. Over time, the page layout, or “Details” section in Lightning pages, can become congested with fields. These fields may well be necessary but not all the time or to all users. Moreover, With Dynamic Forms you’ll be able to:
- Place fields anywhere on the layout without needing to add them to the traditional page layout (“Details” component).
- Use visibility rules to make fields and components appear and disappear based on criteria you choose.
- Do away with multiple page layouts.
- Improve page load times.
From the Winter ‘23 release, Dynamic Forms will support standard objects Accounts, Contacts, Person Accounts and Opportunities. Leads and Cases are on the roadmap for Spring ‘23.
How Do I Set Up Salesforce Dynamic Forms?
1. Create or Migrate a Page
For any custom object, open the Lightning page you wish to upgrade, select the “Record Detail” or “Highlights Panel” component, and choose “Upgrade Now”. Can also create a brand-new page by going to your custom object, selecting “Lightning Record Pages”, then choosing “New”. Once you’ve migrated or created a new Lightning record page, you will see the option to add a “Field Section” component which will then enable to add fields directly to the Lightning record page.
At first, remove the details tab and create a custom tab called “Candidate Information”. Then dragged a “Field Section” component onto tab. The most important you need to add a Fields Component before you are able to add fields!
2. Add Fields to a Component
Once you’ve added a “Field Section” component to your page, you can start to add individual fields. A “Field Section” is added in many places, not just in tabs.
First, let’s add some fields that should always be visible to anyone who views the record:
- Don’t forget to name each field section!
- With a field selected, choose the UI behavior such as “Read Only” or “Required”.
3. Make Fields and Components Conditionally Visible
Both fields and entire field components conditionally visible.
Below, I’ve added a new “Fields Section” component titled “Confidential Information”, and made it visible only to users with the Profile name “HR”:
In edit mode, conditional field will appear once “Willing to Travel” is checked, without the user having to save or refresh the page.
Something noting is that Field visibility and Field Section visibility behave differently. Although both are dynamic e.g., can be set to appear or disappear based on filters you define, Fields are super dynamic as they are evaluated live (as a user makes changes). This means that a field may appear/disappear while a user is editing a record. In contrast, Field Sections are only evaluated on Save, so a new section won’t appear/disappear until the user saves the record.
4. Plan Page Performance
Tabs and accordion load only when selected, so instead of adding lots and lots of “Field Section” components to the initial page (e.g. what shows when you select a record), consider utilizing tabs or the accordion for improved load speed and performance.
This is also to check out any Tips or use the Analyze Button to evaluate your page performance.
5. Add a Mobile Component
You’ll need to add a “Record Detail – Mobile” component to any pages you create so your mobile users can see “Details” fields. This is because the new “Field Section” component is not available on mobile. Any migrated pages will automatically include this component.
As well as setting up Dynamic Forms, you’ll still need to maintain the standard page layout because the mobile interface uses this – not Dynamic Forms!
What’s Not Supported?
- The new Field Section component and the Field components are not supported on mobile. Any migrated pages will automatically have a new “Record Detail – Mobile” component added but you need to remember to add this if you’re building a page from scratch. Dynamic Forms for mobile are expected to be released in Spring ‘23.
- Records created from a Lookup field use the standard page layout (“Details” component), not Dynamic Forms.
For More Blogs: Click Here