Soru

Zorluk: Çok zorDashboard Running User and Visibility Settings

An organization sets the Organization-Wide Default (OWD) sharing setting for the Opportunity object to Private. A Salesforce administrator builds an executive pipeline dashboard stored in a shared dashboard folder that all sales representatives can view. The dashboard is explicitly configured to run as a static user—the Vice President of Sales—who possesses full 'View All' data access across all corporate opportunities.

When a regional sales representative views the dashboard, the dashboard components calculate and display aggregate pipeline totals across all global territories (15M15\text{M}). However, when the same sales representative clicks on a component to drill down into the underlying source report, the resulting report displays only 500000500{}000, consisting strictly of records owned by or shared directly with that sales representative.

Which statement accurately explains the cause of this data discrepancy between the dashboard components and the opened source report?

  1. Dashboard components calculate and display aggregated data based on the security access of the static running user, whereas opening the underlying source report evaluates record accessibility using the logged-in user's own security permissions.Cevap
  2. B
    The dynamic dashboard feature automatically overrides source report folder access and applies role hierarchy filtering whenever a viewer holds a lower role than the specified running user.
  3. C
    Folder access granted on the dashboard level implicitly elevates the logged-in user's record visibility on component summaries, but source report folders require explicit 'Manage' access to view records outside the user's territory.
  4. D
    The Vice President's Field-Level Security (FLS) overrides record sharing rules for dashboard visualizations, while the sales representative's profile settings restrict formula fields on the source report.

Cevap

Dashboard components evaluate data using the security context of the static running user, while navigating to the source report runs the report under the security context of the logged-in user.
The correct explanation accurately distinguishes between how dashboard components and source reports evaluate data security. A static running user dictates the security context for rendering component metrics, allowing viewers to see aggregate data based on the running user's access (in this case, the VP's 'View All' access). However, when a user clicks the component to open the underlying source report, Salesforce enforces standard record security for the logged-in viewer, restricting report rows to only those records accessible under the sales representative's Private OWD access.

Adım Adım Çözüm

1
Analyze the dashboard security configuration context.
The dashboard runs under a static running user (VP of Sales) who has 'View All' permissions on Opportunities.
Static running users determine the data visibility context for all component summaries displayed on the dashboard grid.
2
Evaluate the underlying source report execution context upon user drill-down.
When the sales representative clicks the component, Salesforce executes the source report using the logged-in user's security context.
Source reports always enforce the logged-in viewer's security credentials, Organization-Wide Defaults (OWD), role hierarchy permissions, and sharing rules regardless of the dashboard's static running user setting.
3
Compare component summary values against report drill-down values.
The component reflects the VP's 15Mglobaltotal,whilethesourcereportfiltersresultstotherepresentatives15M global total, while the source report filters results to the representative's 500,000 private allocation.
This behavioral separation between component execution context and source report execution context causes the observed discrepancy.

Anahtar Kavram

Static Dashboard Running User vs. Source Report Execution Context
Bu soruyu puanla