What are Lightning App Builder dynamic forms and dynamic actions, and how do component visibility rules work?
Suggested answer
Dynamic Forms: Enable moving individual fields and field sections out of the page layout and into the Lightning record page directly. Each field or section can have visibility conditions — rules that show or hide them based on record field values, user profile, permission sets, or device type. This replaces the need for multiple page layouts per record type for display-only variations.
Dynamic Actions: Move action buttons from the page layout action bar to the Lightning page, where visibility conditions can be applied per button. Example: Show the "Convert" button only when Status equals "Qualified".
Component visibility rules: Any standard or custom LWC/Aura component placed on a Lightning page can have visibility rules applied in the Properties panel. Condition types include:
— Record field value (equals, not equals, contains, starts with, is null)
— User profile or permission set
— Device form factor (desktop vs mobile)
Multiple conditions can be combined with AND/OR logic. Dynamic Forms require the record page to be configured for a specific object and the feature to be activated for that object in Setup.
Practice content for interview preparation; not an official vendor answer. Verify details against current product documentation.
Community comments (0)
No comments yet.
Sign in or create a free account to add a comment. Comments are moderated before they appear.