With the release of Dynamic Forms, Salesforce has been moving away from its page layout editor. Dynamic Forms is a huge time-saver for admins and developers because it lets you drag individual fields onto your Lightning page and also manage them in a single place. Yet, today, that capability is only available for custom objects.
What if you need to configure conditional visibility on fields for standard objects? Skuid can help.
Conditionally render fields by record type.
One of the most basic elements of great UX is showing only what the user needs to see in order to do their work. Conversely, surfacing items that users can’t do anything with only frustrates them.
With Skuid, you can set logic based on record type to both suppress what users don’t need to see and also provide them with more options on a page. Display logic helps you determine what fields, buttons, sections, and actions are available to your users.
In our webinar example, we showed a list detail page built using Skuid. The page displayed an interactive account list along with contextual KPIs; when you click an account from the list, the page updates the KPIs.
The page included key account details like account name, parent account ID, billing city, industry, and record type ID, and the record types were corporation, school, and special account.
Let’s say you have reps focused on higher education. Because they have nothing with which to populate the parent account ID field on that page, they’ll find it confusing to see it at all. Yet, reps targeting corporations will need to use that field often.
Sellers have one of the toughest jobs out there. Skuid helps you personalize their Salesforce experience by hiding what’s irrelevant to them and showing only what they need to see.
Edit multiple records types inline.
Record types can be used for many different things, from defining page layouts in Salesforce to defining processes. Because of this, one highly requested Salesforce feature is the ability to edit multiple record types inline within a single list view. You can’t do this out of the box yet, but that’s where Skuid can help.
We treat record types like any other reference field. That means you can easily pull record types into Skuid forms and tables, giving you more control to support how your users work.
In the webinar, we showed an account list page that was created using Skuid. In this example, we chose a dropdown field to display the record type, but you can choose any other type of field for display. As we edited the account list, depending on the record type we chose, the next dropdown would only display options relevant to that record type.
Skuid makes this possible because it sits on top of your data model and process automation in Salesforce. And this is one of the benefits of working within the Salesforce ecosystem: we can take advantage of its powerful data modeling capabilities and you can unleash that power with Skuid.
To hear how we answered some great follow-questions from webinar attendees and to see a complete walkthrough, check out the full webinar here.
For more content like this, check out our guide, The most common Salesforce app development challenges and how to solve them.