David Da Moura - 2 months ago
This is more than a "nice-to-have" feature ! We've implemented it on custom objects and it brings user a flawless experience. It is disappointing to tell the users they cannot have the same experience depending on the page (object) they are working on.
Amit Parker - 3 months ago
Easily will be so useful for Cases. For example, as a consultant I've advised many clients. Most clients that do any serious work with cases aka support organizations, end with several case record types and you guessed it several different fields. There is a set of common fields and a set of specific fields. You can do various layouts and then specific records pages etc etc. So much maintenance. One of the places, I ended up doing the basics tab and a specific tab. This approach is pretty much dynamic forms without the flexibility and ease of it. The specifics tab just hosts separate quick action layouts essentially with component visibility filters on them to just show the specific action in the specifics tab. So the use cases are there. I'd love to just dynamically organize field sets without having to maintain a growing list of layouts and lightning record pages and boy oh boy the record page assignments. Once you go to the most granular level managing assignments is so cumbersome! Dynamic forms would make it super easy! On a side not it is just weird that custom objects get dynamic forms ahead of standard objects!
Troy Cantrell - 4 months ago
The addition of the case object to dynamic forms will open the door to significant improvements in the visualization of a case. The complexity of case management in a Service Management environment with ITIL standards would benefit greatly by introducing dynamic forms. Dynamic control of the case display will lend itself to better case management and better control of case details, leading to improved case performance metrics.
Lily Callaghan Smith - 4 months ago
We have multiple teams who support our sales team (e.g. Operations, Finance, Legal) - we use cases to track requests going to each team, and currently do that using Record Types. However, each team has a number of types of requests that come in, so it would be incredibly useful to have fields/section visibility rules based on picklist selections within the page layout. For example, the Operations team do not just take one type of request, and for each different request type, different fields and information is needed to be captured. Adding dynamic form ability to the case layout woud be a great way to improve the support experience within our company.
Lauren Stupar - 4 months ago
We have text fields that only need to be answered when a previous picklist is answered 'yes'. It would make it easier for the user to know which fields need to be answered, if we could hide (or grey out as you can with dependent picklists) the fields that they don't need to complete. Specifically, we would like to have some way to hide or de-epmhasize text (and date) fields until a controlling field is selected 'yes'.
Catherine Deléglise - 4 months ago
Same as Mark Tough : lightning record pages allows us to make dynamic record page based on current user informations or device. But sometimes we just need to create dynamic forms based on record data to simplify the user experience and guide the user. The only point-and-clic solution we have today for standard objects is to create record types and this adds unnecessary complexity for the administrator and the users. We can also code a Visualforce page but it's way too much for such a simple purpose. As using standard objects is supposed to be a priority for a Salesforce Admin it should be a priority to have this functionnality available for standard objects.