From the IdeaExchange: Dynamic Forms for Opportunity Standard Object
This is a continuation of the work that was started based on one of the top IdeaExchange ideas: "Dependent page layouts - data rules to show, hide, or make fields/sections req'd", which resulted in the creation of the Dynamic Forms capability.
Being a Salesforce administrator is hard. But with the addition of Salesforce Dynamic Pages, life got easier for admins everywhere. Dynamic Pages lets you completely customize how and where you place fields in the Lightning App Builder.
Today, Dynamic Pages are only supported for custom objects.record pages. Salesforce plans to roll out Dynamic Pages for a few (but not all) standard objects in its Winter '22 release. But what if you need these capabilities for all standard objects or more complex scenarios like multi-object experiences?
You want your sales people obsessed with the customer experience and your support team engrossed in the cases they’re working. You don’t want them bouncing around Salesforce just to get critical work done, but integrating multiple objects into a single, seamless experience, requires making a custom application with either complex declarative tools or custom code.
The solution: Enhance and extend Dynamic Pages capabilities with Skuid
Let’s say a user needs to see and edit Account information from the record page for a Site (a custom object). They can’t currently do that with Dynamic Pages because Account is a standard object in Salesforce. Besides, they would also need to edit details for two different objects in the same record page. Skuid can bridge those gaps, and in this video, we show you how.
First, pull in the data you need. We use Skuid models to get two different Salesforce objects into one Skuid page. With a model, you can connect to just about any object, standard or custom, and you can have as many models as you need on a Skuid page, letting you access data from multiple locations in one page.
For this example, we use two models—one on the page record object in Salesforce, and one on the Account object. We then add conditions to each model. Conditions are “where” clauses that let you build your query to determine what data to bring into your page.
Add a condition on the first model to get the site record that matches that ID. Then, on the second model, set a condition that looks at the previous model and grab the account that matches the account reference field on that record. Now you’ve created a data layer on the page and the models are talking to each other. Once you establish that connection, you can retrieve the specific fields you want to include on the page.
Once you have the data you want, you can determine how to display it to show the end user the right information at the right time.
You can make a site detail page using a Skuid component called a Form. Drag in a few other Skuid components, and some relevant fields, and then you can show basic account information. If you use the Skuid field property, you can configure the fields and data in any way that’s meaningful to the user.
Once created, drag and display the site detail page within Salesforce Lightning as a component. Now the user can see the related information for the Account object being shown along with the site information, all in one place.
This solution gives you the Dynamic Form experience for standard objects or multiple objects in the same screen.
- Use a Skuid model to pull in multiple objects into one page.
- Build a site detail page with all the fields from any or multiple objects using Skuid.
- Drag your site detail page into Lightning as a component.
- Get the Dynamic Form experience for standard objects or multiple objects in the same screen.
- Make your users happy.