Examkin

Soru

Zorluk: OrtaDashboard Design, Components, and Dynamic Filters

An administrator at a telecommunications provider is assembling an executive dashboard in Lightning Experience using components derived from three distinct report types: Accounts with Subscriptions, Cases with Accounts, and Invoices with Accounts. After adding a dynamic dashboard filter based on the Account Region field from the Accounts with Subscriptions source report, the administrator notices that components driven by the Invoices with Accounts report type do not respond when users select filter values. What is the root cause of this issue, and how should the administrator resolve it?

  1. A
    Dashboard components inherit field security from the viewing user; because users lack Field-Level Security for the region field on invoices, the filter automatically disables component interactivity.
  2. The equivalent region field for the Invoices with Accounts report type was not mapped in the filter configuration; the administrator must edit the dashboard filter settings and select the corresponding field for that source report.Cevap
  3. C
    Dashboard filters cannot filter components whose underlying reports contain summary formulas; the administrator must re-create the invoice report calculations using row-level formulas before filtering.
  4. D
    Filter mapping requires that every source report have identical record type picklist assignments; the administrator must assign matching record types across all objects represented on the dashboard.

Cevap

The equivalent region field for the Invoices with Accounts report type was not mapped in the filter configuration; the administrator must edit the dashboard filter settings and select the corresponding field for that source report.
In Salesforce Lightning Experience, when a dashboard includes components derived from different report types, a dynamic dashboard filter must be mapped to an equivalent field for each report type. If an equivalent field is not selected for a given source report during filter setup, the components linked to that report will ignore the filter selections until the administrator explicitly maps the field.

Adım Adım Çözüm

1
Analyze why dashboard components based on different report types do not respond to a dynamic dashboard filter.
Identify that dynamic dashboard filters require explicit field mapping for each distinct source report type used across components.
Salesforce dynamic dashboard filters are based on a primary field from one report type, but for components using different report types, an equivalent field must be selected manually.
2
Locate the dashboard filter settings in the Lightning Dashboard Builder.
Access the field mapping configuration for the Account Region filter.
The filter configuration panel allows selecting equivalent fields for components whose source reports do not share the exact primary field.
3
Select the equivalent region field on the Invoices with Accounts report type and save the dashboard.
The components based on Invoices with Accounts now react to selections made in the dynamic dashboard filter.
Mapping the equivalent field establishes the data relationship needed for the filter criteria to evaluate against that report type.

Anahtar Kavram

Dashboard Filter Field Mapping Across Multiple Report Types
Bu soruyu puanla

Konular

Dashboard Design, Components, and Dynamic Filters

Bu konudan daha fazla soru