Examkin

Question

Difficulty: HardDynamic Forms and Dynamic Actions

An organization configures a Lightning record page for a custom object using Dynamic Forms. To satisfy internal data privacy requirements, the administrator sets a component visibility rule on the Sensitive Details field section so that it only displays on the UI when the viewing user has the HR Specialist profile. A sales representative whose profile grants Read access to all fields on the custom object generates and exports a standard report containing these records. What will occur regarding the Sensitive Details field when the sales representative views the exported report?

  1. The Sensitive Details field data remains visible in the report because Dynamic Forms component visibility filters affect UI rendering on the record page only and do not restrict data access in reports or APIs.Answer
  2. B
    The Sensitive Details field column displays blank values in the report because Dynamic Forms component visibility rules override Field-Level Security across all Salesforce user interfaces.
  3. C
    The report export fails with an insufficient privileges error because hiding a field section in Dynamic Forms revokes object-level read permissions for non-qualifying profiles.
  4. D
    The administrator must create and assign a new restrictive profile to the sales representative to hide the field in reports, as additive permission sets cannot override Dynamic Forms visibility rules.

Answer

The Sensitive Details field data remains visible in the report because Dynamic Forms component visibility filters affect UI rendering on the record page only and do not restrict data access in reports or APIs.
Dynamic Forms component visibility rules are presentation-layer filters configured in Lightning App Builder. They dictate whether fields or field sections are displayed to a user when viewing a Lightning record page. However, they do not enforce database security. Because the user's Profile grants Field-Level Security (FLS) Read access to the field, standard reports and API exports will continue to show the field data regardless of page layout visibility filters.

Step-by-Step Solution

1
Analyze the scope of Dynamic Forms component visibility rules on Lightning record pages.
Dynamic Forms visibility filters strictly govern whether a field section or field component renders visually on a specific Lightning App Builder record page.
UI component visibility is decoupled from database-level security mechanisms.
2
Evaluate the user's data access permissions via Field-Level Security (FLS) and Profile settings.
The sales representative's profile provides explicit Read access to the field on the underlying object.
Reports fetch record data directly based on object permissions and Field-Level Security, bypassing page layout component visibility.
3
Determine the outcome in the exported standard report.
The field data will be fully populated in the exported report for the sales representative.
Because FLS grants read access, hiding the field visually on a Lightning page using Dynamic Forms does not obscure or sanitize field values in reports.

Key Concept

Decoupling of Dynamic Forms UI Component Visibility from Database Field-Level Security (FLS)
Rate this question

Topics

Dynamic Forms and Dynamic Actions

More questions from this topic