Hot take: I don't like Dynamic Forms

By , Salesforce CTA·1 min read·First shared on LinkedIn,

I know. Everyone else loves them. Salesforce is pushing them hard, and the demos look great. But after years of working with mature Orgs, I see what they turn into once the demo is over.

A Page Layout was boring, and that was its strength. One place to look. An Admin could open it and understand what a user sees in five seconds.

Dynamic Forms spread that logic out. Visibility rules end up on individual Fields in the Lightning Page, and that Lightning Page is assigned per App, Record Type and Profile. Three years later nobody can answer a simple question: "Why can't this user see this Field?"

Is it Field-Level Security? The Page Layout that still exists? A visibility filter someone added to fix one complaint in 2023? Or a second Lightning Page nobody remembers activating?

And the worst part: teams start using visibility rules as if they were security. They're not. A hidden Field is still readable in Reports, List Views and the API.

Dynamic Forms aren't bad technology. The problem is that they make it easy to add complexity quietly, and quiet complexity is exactly what I get paid to remove.

My rule: use Dynamic Forms only when a Record Type or a Page Layout really can't do the job. Keep visibility rules few and simple, and write down why each one exists.

Am I too harsh? Product Owners and Admins, what has your experience been?

Is your Org carrying this kind of dirt?
Book a free 60-minute Salesforce Technical Debt Audit: a score for Usability and Build Quality, and your top cleanup priorities.