Examkin

Question

Difficulty: Very hardDashboard Design, Components, and Dynamic Filters

A Salesforce Administrator is building an executive leadership dashboard in Lightning Experience to monitor cross-departmental operations. The dashboard includes components sourced from three distinct custom report types: 'Opportunities with Products', 'Accounts with Assets', and 'Cases with Solutions'. The administrator needs to configure global dashboard filters and visual component displays. Which TWO statements accurately describe the technical requirements and constraints for this dashboard configuration? (Select 2)

  1. Source reports do not need to share identical field API names to be filtered by a single dashboard filter, as long as the administrator manually maps a compatible data type field from each report type.Answer
  2. A dashboard component configured as a stacked bar chart requires the underlying summary source report to have at least two levels of field groupings defined.Answer
  3. C
    Setting a dynamic dashboard running user to the logged-in user grants viewing users temporary read permissions to inspect aggregated source report records otherwise hidden by Organization-Wide Defaults (OWD).
  4. D
    An administrator can add up to 5 global dashboard filters on a single Lightning dashboard, with each filter supporting up to 100 distinct filter values.

Answer

Source reports do not need to share identical field API names to be filtered by a single dashboard filter as long as compatible data types are mapped, and stacked bar chart components require the source report to have at least two levels of field groupings.
The correct options accurately identify that dashboard filters can map to different field API names across distinct source reports as long as data types are compatible, and that stacked bar chart components require two levels of grouping in the source report to display stacked segments.

Step-by-Step Solution

1
Evaluate dashboard filter mapping mechanics across different custom report types.
Confirm that each dashboard component allows the administrator to choose which field from its underlying source report maps to the global filter. The fields do not need matching API names across different report types as long as data types align.
Salesforce dashboard architecture decouples filter definition from individual source report field names to allow heterogeneous reports on a single dashboard.
2
Analyze grouping prerequisites for multi-dimensional chart components like stacked bar charts.
Determine that stacked bar charts require two grouping levels (X-axis grouping and bar segment stacking grouping).
Without a second grouping level in the underlying report, the component cannot separate data into stacked color segments.
3
Validate security rules for dynamic dashboards and filter limits.
Confirm that dynamic dashboards adhere to user record-level access and that dashboards are limited to 3 filters with 50 values each.
Dynamic dashboards ensure users only see data they are permitted to access based on standard Salesforce security models.

Key Concept

Salesforce Dashboard Component Groupings and Dashboard Filter Field Mapping Constraints
Rate this question

Topics

Dashboard Design, Components, and Dynamic Filters

More questions from this topic