A Salesforce Administrator at an international medical equipment manufacturing company is designing an Executive Maintenance & Sales Dashboard in Lightning Experience. The dashboard aggregates data from three source report types: 'Accounts with Assets', 'Assets with Maintenance Contracts', and 'Contracts with Billing Schedules'. The administrator configures a dynamic dashboard filter based on the 'Account Region' picklist field. During configuration, the administrator notices that components fed by 'Contracts with Billing Schedules' cannot be filtered by 'Account Region'. Which configuration state explains why the dashboard filter cannot be applied to these components?
- The source report type for 'Contracts with Billing Schedules' does not include the Account Region field or any compatible field in its available columns.Answer
- BThe dashboard running user security settings restrict field-level visibility on the Account Region field for end users viewing the contract records.
- CThe source report utilizes a summary formula instead of a row-level formula to evaluate regional groupings across contract records.
- DDynamic Forms component visibility rules on the Contract record page layout have hidden the Account Region field from the active profile.
Answer
The source report type for 'Contracts with Billing Schedules' does not include the Account Region field or any compatible field in its available columns.
For a dynamic dashboard filter to apply to a component, the source report used by that component must include a field that is compatible with the filter field type. If the underlying report type ('Contracts with Billing Schedules') does not contain the 'Account Region' field or an equivalent field in its layout, the administrator cannot map the dashboard filter to that component.
Step-by-Step Solution
Key Concept
Dashboard Filter Field Mapping Prerequisites