Northern Trail Outfitters uses a custom Compensation object to track employee commissions. An administrator configured Dynamic Forms on the Lightning record page and added a component visibility filter to the 'Bonus Amount' field so that it only renders on the page when the viewing user's role is 'Sales Manager'. A user with the 'Sales Rep' role views a standard report that includes the 'Bonus Amount' column. Assuming the Sales Rep has Read access to the field via Field-Level Security (FLS) on their profile, which outcome occurs when the Sales Rep views the report?
- The user sees the 'Bonus Amount' values in the report because Dynamic Forms visibility filters affect only component rendering on the Lightning record page, not reporting or API data access.Answer
- BThe user sees blank values for the 'Bonus Amount' field in the report because Dynamic Forms component visibility rules automatically restrict data access globally across all reports and dashboards.
- CThe user receives a security permission error when running the report unless the administrator creates and assigns a separate profile that hides the report folder.
- DThe 'Bonus Amount' column is automatically hidden from the report because component visibility filters temporarily revoke field-level security when the page filter condition evaluates to false.
Answer
The user sees the 'Bonus Amount' values in the report because Dynamic Forms component visibility filters affect only component rendering on the Lightning record page, not reporting or API data access.
Dynamic Forms component visibility filters are presentation-layer controls that specify when a field or section appears on a Lightning record page. They do not override or modify Field-Level Security (FLS). Because the user has Read access to the field through FLS, the data remains accessible in reports, list views, search results, and API integrations.
Step-by-Step Solution
Key Concept
Dynamic Forms Component Visibility vs. Field-Level Security
Estimated Time:1m 30s