Soru

Zorluk: OrtaDashboard Design, Components, and Dynamic Filters

A Salesforce Administrator at a freight logistics company is designing a Lightning Experience Operations Dashboard to monitor regional fulfillment cases and sales opportunities. The administrator plans to add dynamic dashboard filters to allow leadership to segment dashboard data by Region and Account Type. Which two considerations or configuration requirements must the administrator keep in mind when implementing dynamic filters on this dashboard? (Select 2)

  1. A single Lightning dashboard can include a maximum of 3 dynamic filters, with each filter supporting up to 50 filter values.Cevap
  2. B
    Dynamic dashboard filters grant logged-in users visibility into underlying records that are otherwise hidden from them by Organization-Wide Defaults.
  3. Each source report component on the dashboard must contain fields compatible with the selected filter attribute or have its filter field manually mapped in the component settings.Cevap
  4. D
    Dynamic dashboard filters require all source reports to use summary formulas instead of row-level formulas to process filter values across grouped records.

Cevap

The correct requirements are that a Lightning dashboard supports a maximum of 3 dynamic filters with up to 50 filter options each, and that each dashboard component's source report must have compatible fields mapped to the filter criteria.
The option stating that a single Lightning dashboard supports a maximum of 3 dynamic filters with up to 50 values each is correct because this matches Salesforce system limits. The option stating that each source report component must have compatible fields mapped is also correct because filters require corresponding report fields to accurately restrict component data.

Adım Adım Çözüm

1
Identify the system limit for dynamic filters in Salesforce Lightning Experience dashboards.
Confirm that a maximum of 3 filters can be added to a single dashboard, with up to 50 filter options per filter.
This is a standard platform governance limit for dashboard design in Lightning Experience.
2
Evaluate field mapping requirements for multi-component reports driven by dashboard filters.
Determine that each source report component must have a matching field type mapped to the dashboard filter criteria.
If a source report lacks a matching field or mapping, the filter cannot refine that specific component's data.
3
Verify security and formula dependencies.
Confirm that dynamic filters respect existing sharing settings and do not rely on summary formula definitions.
Filters narrow visible dataset subsets without granting expanded record permissions or altering report formula structures.

Anahtar Kavram

Dashboard Dynamic Filters and Component Field Mapping
Bu soruyu puanla