Does anyone have any idea of the feedback so far for the Full View record page view? I like the look of it much more than the Grouped View. Is it available for production to use at your own risk? I saw some documentation online that says "Full view is not available for all org configurations (for example, if an org has a large number of fields or related lists)". What is a "large number of fields or related lists" to SF?
Glad to hear @Sujay Nandan Nadkarni and thank you for chiming in! The general guidance around performance is more around the # of fields you have, and not so much about Grouped vs Full view. The views have different performance characteristics in that they load different components initially, but any given component will perform the same at the end of the day.
@Tim Plucinski you can use it in production no problem. You can even create your own Full view equivalent page via Lightning App Builder so Full view itself is nothing new, and is made up of GA components. The official guardrails are conservative at >50 fields or 12 related lists on any page layout, this is the 75th percentile. Our goal here is to have orgs with larger numbers of fields to take a moment to consider if they can break them up, regardless of default page configuration. However, my personal experience has shown that if you are under 150 fields the page load performance characteristics are on par with Grouped view. Once again, it's about components on the page and when you load them ultimately. Note Grouped View hides fields behind a click, so if you need to get your fields, you'll still need to pay the cost to load them. Hope that helps. Best way is to test it out for yourself, figure out what is best for your users, if its Grouped view, Full view, or a custom configuration, and making sure what you have works and feels good to you.
