#Dynamic Forms0 personne en discute

The OP is asking about setting the default tab by User or Profile, NOT cloning and assigning a whole new Lightning record page to manage for every single set of users!  This is the Salesforce administrative nightmare / disaster we're already stuck with and defeats much of the purpose of using Dynamic Forms / Lighting Record Pages over Classic layouts to begin with. Another huge gap with Dynamic Forms from Salesforce (4+ years and waiting).  What good is trying to use Dynamic Forms if you still have to default everyone to the same tab OR are still stuck with "layout sprawl" cloning pages just to land Sales on the Sales tab, Marketing on the Marketing tab, etc.?  

Please upvote this on the IdeaExchange and let's hope it gets some attention by Salesforce so we can actually start using Dynamic Forms in any meaningful way to cut down on page layouts.  

#Salesforce #Salesforceadmins #Dynamic Forms

@Cheryl Feldman

Thank goodness it does NOT automatically convert all your pages.  I'd highly suggest first testing this in your org on a per object / page layout (and Record Type, if you plan to attempt to use them to replace RTs) basis to make sure Dynamic Forms works for you. I certainly still find them unusable and not really "GA ready" despite being billed as such, due to gaps and insanely sluggish UI behavior including:

- Usability issues: Lightning page editor hanging/bugging out often for 5-10 seconds at a time as you drag fields around if you have more than 20 or so fields visible...painfully SLOWWWWW and sometimes LEX just crashes while trying to move fields around (no, we do not have any Apex or custom code...just standard Lightning components)

- Poor non-WYSIWYG design issues: Insists on spread out, "Comfy" (read: horrid) layout even when your profile is configured for Compact layout....again, prepare for endless scrolling and good luck trying to stick a field between fields 25 and 26 on a page....get yourself some coffee and a carpal tunnel brace

- Feature Gap #1: No "Blank Space" to align columns horizontally (NO, the "Align fields" checkbox is so basic and classic has been doing this for 20 years...this still does not solve many basic field alignment issues)

- Feature Gap #2: Collapsed sections do not stay collapsed when you refresh a page (super annoying, especially if you're a SF admin or power user constantly using SF all day & want to be able to keep 5-7 sections or 100 fields you never look at collapsed--without creating horizontal "tab sprawl" by moving each section to its own tab--so you can just focus on your tasks/data points at hand)

#Dynamic Forms

@James Dougherty

The system right now doesn't allow a blank value for Equal or NOT Equal, I've just tried a fallback rule (Rule 5) set to Always. I also tried this as =! Gold, Platinum, Bronze or Silver. When the field was blank it did not display any icon. I suspect this is a limitation considering the feature is in it's infancy, the last option would be to use a formula field in a condition instead but that may not work.

If you need more targeted support then feel free to post a question and tag me in the body of your post.

@K S From what I can see you do not have the fields with normal behavior being displayed under the opposite condition.

You are adding visibility criteria to that Field component itself, not to the behavior. So you would need to add a second instance of that Field component to show when the conditions of the required component are not met.

Here is a very simplified example:

I have a checkbox field and sample picklist field. I added in an instance with no UI behavior (normal) to display when that field is not required and then a second instance to display when that checkbox is checked to make the field show as required.