Examkin

Soru

Zorluk: Çok zorLightning App Builder Pages (App, Home, Record Pages)

Universal Containers utilizes Dynamic Forms on a custom Opportunity Lightning Record Page. An administrator configures a component visibility rule on the Sensitive_Margin__c field component to render only when StageName is set to 'Closed Won'. A sales user whose profile has Field-Level Security (FLS) Read access unchecked for Sensitive_Margin__c opens an Opportunity record that is in 'Closed Won' stage. The custom record page is activated as the App Default for the 'Sales Central' app. Which outcome will the sales user experience upon opening this record in the 'Sales Central' app?

  1. The user will not see the Sensitive_Margin__c field because Field-Level Security (FLS) restrictions supersede Lightning App Builder component visibility filters.Cevap
  2. B
    The user will see the Sensitive_Margin__c field because Dynamic Forms component visibility rules override object-level and profile-level Field-Level Security.
  3. C
    The user will see a page rendering error because App Default activations require all custom fields with visibility filters to have picklist assignments configured per record type.
  4. D
    The user will be granted read access to the field because activating a page as an App Default creates an implicit permission set for all assigned app users.

Cevap

The user will not see the field because Field-Level Security restrictions supersede Lightning App Builder component visibility filters.
Field-Level Security (FLS) is enforced strictly at the database layer. Even if a field component's visibility conditions on a Dynamic Forms page are fully met, Salesforce will withhold the field from any user who lacks Read FLS permissions for that field.

Adım Adım Çözüm

1
Evaluate the Field-Level Security (FLS) settings for the user profile.
The user profile has Read FLS access set to unchecked for the field.
Salesforce security architecture enforces FLS at the data level prior to rendering any presentation layer components.
2
Evaluate the Dynamic Forms component visibility filter on the Lightning Record Page.
The stage condition ('Closed Won') evaluates to true for the record.
Component visibility filter rules dictate when a component is eligible to appear in the UI.
3
Determine the final field visibility by combining FLS and UI component rules.
The field remains hidden from the user.
Component visibility cannot bypass or override FLS. If FLS restricts access, the field is hidden regardless of component visibility criteria.

Anahtar Kavram

Field-Level Security vs Dynamic Forms Component Visibility
Bu soruyu puanla

Konular

Lightning App Builder Pages (App, Home, Record Pages)

Bu konudan daha fazla soru