Question

Difficulty: HardDashboard Design, Components, and Dynamic Filters

A Salesforce Administrator is configuring a customer success dashboard containing six components fed by three distinct report types: Accounts with Contracts, Opportunities with Products, and Cases with Assets. The administrator adds a dynamic dashboard filter based on the Account Region field. During testing, four chart components update when a regional filter is applied, but two table components ignore the selection and continue displaying global records. What is the root cause of this behavior, and how should the administrator resolve it?

  1. The source reports for the two table components do not automatically map to the filter field, requiring the administrator to edit the filter settings and select the equivalent field for those specific components.Answer
  2. B
    The dashboard running user security settings overwrite dynamic filters whenever table components contain records from multiple object hierarchies.
  3. C
    The table components utilize summary formulas that calculate metrics globally, which disables dashboard field filtering on those components.
  4. D
    Dynamic Forms component visibility rules on the underlying record pages are suppressing field filter propagation to multi-object dashboard layouts.

Answer

The source reports for the two table components do not automatically map to the filter field, requiring the administrator to edit the filter settings and select the equivalent field for those specific components.
When adding dynamic filters to a dashboard built on multiple report types, Salesforce attempts to auto-map the filter field to equivalent fields in each source report. If an equivalent field is not automatically recognized for a component's source report, the administrator must edit the dashboard filter settings and manually assign the matching field for that component.

Step-by-Step Solution

1
Analyze why dynamic dashboard filters apply to some components while ignoring others.
Dynamic dashboard filters rely on mapping a chosen filter field (e.g., Account Region) to a corresponding field in each component's underlying source report.
When components use different report types, field names or relationships may differ across reports.
2
Identify the configuration steps required when report types differ.
The administrator must open the dashboard filter properties and select the equivalent field for the components that did not automatically map.
If no equivalent field is mapped for a component, that specific component ignores the dashboard filter selection.

Key Concept

Dashboard Dynamic Filter Field Mapping across Multiple Source Report Types
Estimated Time:2m 0s
Rate this question