Salesforce Dynamic Forms: Your Top 12 Questions Answered

Share this article...

Salesforce Dynamic Forms has been in general release for a year and it’s still a hot topic. While Salesforce is continually working on enhancing this feature, Admins everywhere are learning how best to use it, which has led to a lot of questions. In this article we’ll dive into our top 12 questions about Dynamic Forms to help you make the most out of this amazing tool.

For a full guide, check out our “Salesforce Dynamic Forms – Overview & Deep Dive Tutorial”.

”Eelements.cloud”

1. Is Dynamic Forms available in Classic?

No! Dynamic Forms is only available in Lightning Experience. If you’ve been looking for an excuse to migrate, this might just be it.

Read More: Salesforce Classic vs. Lightning – Is Anything Still Missing?

2. Is Dynamic Forms available for standard objects?

Dynamic Forms are not available for standard objects in Salesforce – they are currently only available for custom objects.

Due to the complexities of standard objects, Salesforce is working with various internal teams to roll out this feature for the most requested standard objects. That’s right…it’s being done on an object by object basis, so don’t expect Dynamic Forms to be available for all standard objects any time soon. Check out this chatter post to learn how you can upvote Dynamic Forms for your favourite standard object.

3. Do I still need the standard page layout?

Yes, not only can you update the standard page layout, you need to. The standard page layout still controls things such as which Related Lists are visible on your Lightning page layout.

On the Candidate object, I have not added the ‘Files’ related list to my page layout:

When I try to edit my Lightning page layout, although I can see the ‘Files’ related list, when I drag it onto the page it displays an error to explain it cannot be displayed because it is not included in the page layout:

It’s also worth noting that a record’s printable view is based on the fields from the default page layout, not the fields on the Dynamic Forms page. In addition, the mobile layout is also driven by the standard page layout.

4. What if I have the standard detail page component plus Dynamic Form elements such as sections and fields?

There’s nothing stopping you from having both the standard detail component, as well as Dynamic Form sections and fields. However, more components will impact the page load time, plus you’ll have duplicate fields. You also need to consider what will display when a user creates a new record…see the next question for more information.

Read More: The Analyze Button: Improve Your Salesforce Lightning Page Load Speed

5. Which is used when creating a record: the details page or Dynamic Forms elements?

This is a slightly complicated question and it varies depending on where/how you create a record.

Typically, once Field Section components are included in the Lightning page layout, then they are used to create a new record, not the details component. If you select the ‘New’ option from the object tab, it will use the Dynamic Forms elements, not the details page.

My Candidate Lightning page contains both the details component, as well as dynamic Field Sections and Fields:

When I try to create a new Candidate record from the relevant tab, I am presented with the Dynamic Field Sections and Fields only:

That said, if you create a record from a lookup, the fields come from the record detail component, not from the Dynamic Forms fields on the page. Check out the third bullet point on Dynamic Forms Known Issues.

6. What happens if you hide a mandatory field?

Chaos. Well, that’s not entirely true, but it does make for a very unpleasant user experience. In short, the user will not be able to save in order to create or edit, and will receive an error.

Salesforce will warn you not to do this…

And if you persist, your users will see this…

Don’t say you haven’t been warned!

7. Do section headings remain, even if all fields are hidden?

Yes. Even if all the fields in a section are hidden, the section header will still be visible. Consider adding your filter to the component instead of individual fields if you want the entire section, including header, to be hidden.

8. Can you filter by record type?

Yes, you can. For this, you’ll need to select ‘Advanced’ when adding your filter.

9. Can you filter by multiple picklist values?

Yes, you can. This is not to be confused with filtering by multi-select picklists (see question below).

What we mean here is can you filter on multiple picklist values e.g. if you have a picklist field ‘Rating’ with the values ‘Hot’, ‘Warm’ and ‘Cold’, can you create a filter to display only if the field value is ‘Hot’ or ‘Warm’?

Simply add two filters and set the filter logic as 1 OR 2.

10. Can I use multi-select picklists for filters?

No. You cannot filter on multi-picklist fields.

11. Can I use fields from the parent record as filters on Dynamic Forms?

Yes you can. When you set component visibility, click ‘Add Filter’, then select ‘Advanced’. In my developer org I have two custom objects: Role and Candidate. Role is the parent object and Candidate the child object.

By navigating to ‘Advanced’, I am able to select ‘Record’ which then displays all fields available on Candidate including the lookup to Role. I select ‘Role’ and am then able to choose a field on the Role object called ‘Level’ to use as a filter on my Candidate page layout.

A word of caution when using this functionality; when creating a new record, even with the parent record selected (e.g. referenced in a lookup), values aren’t calculated until you save.

What does this mean in terms of the functionality you can expect? It means that if you have Field Sections or Fields that are filtered based on values in a parent record, they will not be visible until after the new record is saved.

12. What about Field visibility vs Field Section visibility?

Something worth 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.

Summary

We love Dynamic Forms and hope that you do too! There are many exciting enhancements to expect from Dynamic Forms over the next few releases. Do you have any other pressing questions about Dynamic Forms? Pop them in the comments below!

Resources

”RevenueGrid”

3 thoughts on “Salesforce Dynamic Forms: Your Top 12 Questions Answered

  1. A workaround for filtering on Multi-Select picklists is to create a text formula field that concatenates the selected values into a comma or semicolon separated string.

    Multi-Select Field(String) (Multi_Select_Field_String__c)
    IF(INCLUDES(Multi_Select_Field__c, “PicklistValue1”), “PicklistValue1;”, null) +
    IF(INCLUDES(Multi_Select_Field__c, “PicklistValue2”), “PicklistValue2;”, null) +
    IF(INCLUDES(Multi_Select_Field__c, “PicklistValue3”), “PicklistValue3;”, null)

    Then you can filter on that text field using the Contains operator.
    Multi-Select Field String Contains PicklistValue1

    The drawback to this workaround is that the formula won’t calculate until the record is saved, so the dynamic form won’t update in real-time as values are selected or removed from the multi-select picklist. This solution works best when you need to display or hide whole sections on your page layout

  2. #11 IMO is something that needs to be corrected sooner then later. Picture having a Order / Order Line Item. In the OLI you want to lookup a product. If you want to filter fields related to the selected product you have to create the OLI then Save. Then when you reopen the OLI the visibility works and if one of the fields was required in dynamic forms you will see the record saved and will not enforce this until the second save. This is silly , common Sales Force get this fixed !
    Also would be nice if you get the fields feature out of beta on Flows.

  3. One thing that needs to be dealt with is the time it takes to rearrange. I have a section that needs to be combine with another section. On a standard page layout I’d just drag all the fields at once to their new section. However on dynamic forms I have to move each individual field to it’s section. This would be less of a burden if the page scroll was a bit better. I’m constantly “pushing” the dragged field against the border to get the page to scroll. Just overall a real pain in the butt.

Add Comment