Question

Difficulty: MediumDynamic Forms and Dynamic Actions

A System Administrator configures a Lightning Record Page for a custom Warranty Claim object using Dynamic Forms. The administrator sets a component visibility rule on the 'Reimbursement Amount' field so that it only displays on the page when the 'Claim Status' field is set to 'Approved'. A user whose Profile grants Read and Edit access to 'Reimbursement Amount' via Field-Level Security (FLS) runs a Salesforce report that includes Warranty Claims currently in 'Draft' status.

Which data visibility behavior will the user observe in the report for the 'Reimbursement Amount' field?

  1. The user can view the 'Reimbursement Amount' values for 'Draft' records in the report because Dynamic Forms visibility filters control UI layout display only, not database level or report visibility.Answer
  2. B
    The 'Reimbursement Amount' field column will appear completely blank for all 'Draft' status records in the report because Dynamic Forms rules override Field-Level Security settings.
  3. C
    The user will receive an 'Insufficient Privileges' error message upon running the report because it contains fields dynamically hidden from their current record view.
  4. D
    The user must be assigned a Permission Set granting 'View All Data' to bypass Dynamic Forms visibility and see the field values in reports.

Answer

The user can view the field data in the report because Dynamic Forms visibility filters apply only to Lightning Record Pages and do not restrict report data access.
Dynamic Forms component visibility rules control whether a field or section appears on a specific Lightning Record Page based on filter criteria. They do not affect data access rules. Because the user has Field-Level Security access to the field, the report will display the field data regardless of the record's status or page layout visibility rules.

Step-by-Step Solution

1
Analyze the scope of Dynamic Forms visibility rules.
Dynamic Forms visibility rules are evaluated client-side to conditionally display components, sections, or fields specifically on Lightning App Builder pages.
Understanding the boundary between UI display rules and data security mechanisms is essential.
2
Evaluate Field-Level Security (FLS) vs. UI display controls.
The user has explicit Read/Edit FLS on their profile. FLS is the governing security mechanism for data visibility across reports, list views, and API calls.
Field-Level Security secures data regardless of how or where a field is hidden on a page layout.
3
Determine report output behavior.
Because reports bypass Lightning Page layout visibility logic and rely on FLS, the user will see all field data in the report.
Dynamic Forms filters do not alter database query behavior or report generation.

Key Concept

Dynamic Forms UI Visibility vs. Field-Level Security (FLS)
Estimated Time:1m 30s
Rate this question