Dynamic Dashboards and Dashboard Filters
5 minutes
5 Questions
Dynamic Dashboards and Dashboard Filters are two key features Salesforce Platform Administrator II candidates must understand within Data and Analytics Management. Dynamic Dashboards display data based on the security settings of the user viewing them, rather than a fixed 'running user.' Normally, a dashboard runs as a specific user, meaning everyone sees the same data that user can access. With a dynamic dashboard, the 'View dashboard as' option is set to 'The dashboard viewer,' so each person sees only the records their own sharing rules, role hierarchy, and field-level security permit. This eliminates the need to create multiple copies of the same dashboard for different roles or regions. Important limits: Salesforce restricts the number of dynamic dashboards per org by edition (for example, up to 5 in Enterprise, 10 in Unlimited and Performance, with additional ones purchasable). Dynamic dashboards cannot be scheduled for refresh or emailed on a schedule, and they cannot be saved in private folders. Administrators can also allow viewers to choose a running user if they have the 'View My Team's Dashboards' permission. Dashboard Filters let users interactively narrow the data shown across all components on a single dashboard without editing the underlying reports. An admin adds a filter on a common field (such as Region, Industry, or Owner) and defines filter values or ranges. When a viewer selects a value, every component built on a report containing that field updates simultaneously. Each dashboard supports up to three filters, and each filter can have up to 50 values. Filters work only on fields available in all source reports; components based on reports lacking the field are unaffected. Filters cannot be applied to dashboards built from joined reports in older configurations, and scheduled refreshes always use the unfiltered view. Together, these features reduce dashboard duplication, improve maintainability, and deliver personalized, secure analytics to many users from one centralized asset.
Dynamic Dashboards and Dashboard Filters: A Complete Guide for the Salesforce Advanced Administrator Exam
Why This Topic Matters
Dashboards are the primary way executives, managers and reps consume Salesforce data, and the Advanced Administrator exam expects you to design dashboards that scale securely across an entire organization. Two features sit at the heart of this: dynamic dashboards, which show each viewer data based on their own security access, and dashboard filters, which let users slice a single dashboard by region, product, period or any other common field. Together they allow an administrator to replace dozens of near-identical dashboards with one well-designed dashboard, reducing maintenance, protecting data visibility and keeping the org under its dashboard limits. In the exam's Advanced Data and Analytics Management section, these topics appear frequently in scenario questions, so you must know not only what each feature does but also its limits, required permissions and the situations where one is a better fit than the other.
Part 1: Dynamic Dashboards
What a Dynamic Dashboard Is
Every dashboard has a running user, the user whose record access and sharing rules determine the data shown in the components. A standard (static) dashboard has a single fixed running user; everyone who can access the dashboard folder sees exactly the same numbers, calculated as if they were that user. A dynamic dashboard instead sets the running user to the dashboard viewer (in Setup language, View dashboard as: The dashboard viewer). Each person who opens the dashboard sees only the records that their own profile, role, sharing rules and field-level security allow them to see.
The Three Running User Options
When you edit dashboard properties you choose one of the following:
1. Me (a specific named user, typically the creator): a static dashboard. All viewers see data as this user. This is the option that can accidentally over-expose data if the running user has broad access and the dashboard folder is widely shared.
2. Another person: still static, but the running user is someone else, for example a VP of Sales. You can also tick Let dashboard viewers choose whom they view the dashboard as, which allows users with the View My Team's Dashboards or View All Data permission to switch the running user to a subordinate.
3. The dashboard viewer: this is the dynamic dashboard. The logged-in user is always the running user.
How It Works
When a dynamic dashboard is opened, Salesforce runs the underlying source reports in the context of the viewer. Role hierarchy, sharing rules, organization-wide defaults, manual shares and team membership are all respected. A sales rep sees only their own opportunities, their manager sees the whole team, and the VP sees the entire region, all from one dashboard with one set of components. Because the data is calculated at view time for each individual, a dynamic dashboard cannot have a single cached snapshot shared by everyone, which drives several of its restrictions.
Key Limits and Restrictions You Must Memorize
- Number per org: Enterprise Edition allows up to 5 dynamic dashboards, Unlimited and Performance Editions allow up to 10, and Developer Edition allows up to 3. Additional dynamic dashboards can be purchased from Salesforce. The limit is on dynamic dashboards only; static dashboards are not counted.
- No scheduled refresh: Dynamic dashboards cannot be scheduled to refresh and cannot be subscribed to for emailed snapshots. They must be refreshed manually when viewed, because there is no single running user whose data could be sent.
- No private folders: A dynamic dashboard cannot be saved to a user's private dashboards folder; it must live in a shared folder.
- Permission to create: The Manage Dynamic Dashboards permission is required to create, edit or delete a dynamic dashboard. To set the running user to another specific person you need View All Data, or View My Team's Dashboards if that person is below you in the role hierarchy.
- Chatter and following: In Salesforce Classic, dashboard components on dynamic dashboards cannot be followed or posted as snapshots to Chatter in the same way as static components, because the values differ per user.
- Folder access still matters: A dynamic dashboard controls what data a viewer sees, but folder sharing controls whether they can open the dashboard at all. You still need to share the folder appropriately.
When to Recommend a Dynamic Dashboard
Choose a dynamic dashboard when the requirement is that different users should see different data from the same layout, driven by their own record access. Typical phrasing in a scenario: each sales rep should see only their own pipeline, managers should see their team, and the company wants to avoid creating one dashboard per rep. A dynamic dashboard is also the secure choice when a static running user would reveal records a viewer is not normally allowed to see.
Part 2: Dashboard Filters
What a Dashboard Filter Is
A dashboard filter is a picklist-style control at the top of a dashboard that lets a viewer narrow every component at once by a chosen field value, for example Region equals West, or Close Date equals This Quarter. Instead of cloning a dashboard for each region, product line or fiscal period, you build one dashboard and let users apply filters interactively. Filters change the slice of data displayed; they do not change the security context, so they are often combined with a dynamic dashboard to get both personalization and interactivity.
How Dashboard Filters Work
- You add filters in the dashboard editor by selecting a field. In Lightning Experience you pick the field from one of the source reports and Salesforce automatically maps equivalent fields on the other components' source reports (for example, Account Industry on an Opportunity report and Industry on an Account report).
- You then define the filter values (also called filter options). Each value has an operator and a value, such as equals, not equal to, greater than, less than, contains, starts with, or for dates, relative values like LAST QUARTER or THIS YEAR. You can group multiple criteria into a single option, for example a single option named Enterprise that means Annual Revenue greater than 10,000,000 OR Number of Employees greater than 1,000.
- When a viewer selects a value, every component whose source report contains the filter field is re-run with that condition appended. Components whose source report does not include the field are not filtered and continue to show unfiltered results; the editor warns you about this when you set the filter up.
- When a user drills from a filtered component into the source report in Lightning Experience, the dashboard filter is carried into the report view so the numbers match.
- The last-used filter selection is remembered for the user when they return to the dashboard.
Key Limits and Restrictions You Must Memorize
- A dashboard can have up to 3 filters.
- Each filter can have up to 50 filter values (options).
- Filters apply only to report-based components; they are not applied to Visualforce components or custom s-controls.
- Filter fields must exist on (or be equivalent to a field on) the source reports. If the field is missing from a report, that component is unaffected.
- Bucket fields cannot be used as dashboard filter fields; bucket fields exist only within a report. The workaround is to recreate the grouping logic as a filter option with multiple criteria, or to use a formula field on the object.
- Filters are not applied to scheduled refreshes or subscription emails; the emailed or refreshed snapshot always reflects the unfiltered dashboard.
- Filters work on standard and custom fields of most types: picklist, text, lookup/ID, number, currency, checkbox and date/datetime.
- Dashboard filters do not override sharing or field-level security; they only narrow what the running user can already see.
When to Recommend Dashboard Filters
Choose filters when the requirement is that the same user wants to toggle between views of the data, for example switching between regions, product families or time periods, or when the org wants to reduce dashboard sprawl without needing per-user security. Filters are also the right answer when an org has already used up its dynamic dashboard allocation and needs flexibility without purchasing more.
Part 3: Dynamic Dashboards versus Dashboard Filters
Purpose: Dynamic dashboards personalize security context (what each person is allowed to see). Filters personalize scope (which subset a person chooses to look at).
Who controls the view: Dynamic dashboards are automatic based on login; filters are chosen manually by the viewer.
Scheduling: Static dashboards with filters can be scheduled and subscribed to (unfiltered); dynamic dashboards cannot be scheduled at all.
Limits: 5/10/3 dynamic dashboards per edition versus 3 filters and 50 values per filter on any dashboard.
Combination: A dynamic dashboard can also have filters. Example: a single Sales Performance dashboard where each rep sees only their own records (dynamic) and can switch between This Quarter and Last Quarter (filter).
Part 4: Common Scenario Patterns and the Correct Answers
Scenario: A company with 200 sales reps wants each rep to see a dashboard showing only their own opportunities without the admin building 200 dashboards. Answer: Create one dynamic dashboard with the running user set to the dashboard viewer and share the folder with the sales profile.
Scenario: The regional VP wants to open the sales dashboard and switch between the North, South, East and West regions. Answer: Add a dashboard filter on the Region field with one filter value per region.
Scenario: An Enterprise Edition org tries to create a sixth dynamic dashboard and receives an error. Answer: The org has hit the limit of 5 dynamic dashboards; either convert an existing one to static, use dashboard filters on a static dashboard, or purchase additional dynamic dashboards.
Scenario: Management wants a dynamic dashboard emailed to all managers every Monday morning. Answer: Not possible; dynamic dashboards cannot be scheduled or subscribed to. Recommend a static dashboard with an appropriate running user, or have managers refresh manually.
Scenario: A filter on Industry applies to four components but one component still shows all records. Answer: The source report for that component does not contain the Industry field or an equivalent field; add the field to the report or accept that the component is unfiltered.
Scenario: A user needs to add a fourth filter for Product Family. Answer: Cannot be done; the maximum is 3 filters. Consider combining criteria into a single filter option, creating a separate dashboard, or using a dynamic dashboard to reduce the need for one of the existing filters.
Scenario: An administrator cannot find the option to set the running user to the dashboard viewer. Answer: The admin lacks the Manage Dynamic Dashboards permission, or the dashboard is in a private folder.
Scenario: A dashboard with the running user set to the CEO is shared with all internal users and reps are now seeing confidential deals. Answer: This is a data exposure caused by a static running user; convert it to a dynamic dashboard or change the running user and restrict folder access.
Scenario: A user wants to filter a dashboard on a bucket field they created in a report. Answer: Bucket fields cannot be dashboard filter fields; create a formula field on the object or build a multi-criteria filter option.
Exam Tips: Answering Questions on Dynamic Dashboards and Dashboard Filters
1. Decode the keywords. Phrases such as each user should see only their own data, based on their role, without creating a dashboard for each person or respect sharing settings point to a dynamic dashboard. Phrases such as switch between, toggle, select a region or period, same user wants different views point to dashboard filters.
2. Memorize the numbers. Dynamic dashboards: 5 in Enterprise, 10 in Unlimited and Performance, 3 in Developer. Filters: 3 per dashboard, 50 values per filter. Numeric limits are among the easiest points to win or lose.
3. Remember what cannot be done. Dynamic dashboards cannot be scheduled, subscribed to, or saved in private folders. Filters cannot be applied to Visualforce components, bucket fields, or to scheduled and emailed snapshots. If an answer option proposes one of these, it is usually a distractor.
4. Know the permissions. Manage Dynamic Dashboards to create them; View All Data or View My Team's Dashboards to set another person as running user or to let viewers choose the running user. Questions about a missing option are often really permission questions.
5. Separate data access from dashboard access. The running user governs what data appears; folder sharing governs who can open the dashboard. A correct answer often involves both, for example create a dynamic dashboard and share the folder with the relevant public group.
6. Watch for data exposure traps. If a scenario describes users seeing more data than they should, suspect a static running user with broad access combined with wide folder sharing. The fix is a dynamic dashboard or a more appropriate running user, not a sharing rule change.
7. Check the source reports when a filter misbehaves. A filter that does not affect one component almost always means the filter field is missing from that component's source report. Equivalent field mapping only works when the field exists.
8. Consider combining both features. When a scenario asks for personalized security plus interactive slicing, the best answer is a dynamic dashboard with filters, not one or the other.
9. Eliminate overbuilt answers. Options suggesting one dashboard per user, per region or per period, or custom code such as Visualforce or Apex, are rarely correct when a dynamic dashboard or a filter solves the problem declaratively with less maintenance.
10. Think like a consultant. The Advanced Administrator exam rewards solutions that are scalable, secure and low-maintenance. When two options both technically work, pick the one that reduces the number of dashboards, respects existing sharing and stays within org limits.
Quick Reference Summary
- Dynamic dashboard = running user is the dashboard viewer; data reflects each viewer's own access.
- Requires Manage Dynamic Dashboards; must be in a shared folder; cannot be scheduled or subscribed.
- Limits: 5 (Enterprise), 10 (Unlimited/Performance), 3 (Developer); more can be purchased.
- Dashboard filter = up to 3 per dashboard, up to 50 values each, applies to components whose source report has the field or an equivalent.
- Filters do not apply to Visualforce components, bucket fields, or scheduled/emailed dashboards, and never override sharing.
- Use dynamic dashboards for who sees what; use filters for which slice to view; combine them for both.
Dashboards are the primary way executives, managers and reps consume Salesforce data, and the Advanced Administrator exam expects you to design dashboards that scale securely across an entire organization. Two features sit at the heart of this: dynamic dashboards, which show each viewer data based on their own security access, and dashboard filters, which let users slice a single dashboard by region, product, period or any other common field. Together they allow an administrator to replace dozens of near-identical dashboards with one well-designed dashboard, reducing maintenance, protecting data visibility and keeping the org under its dashboard limits. In the exam's Advanced Data and Analytics Management section, these topics appear frequently in scenario questions, so you must know not only what each feature does but also its limits, required permissions and the situations where one is a better fit than the other.
Part 1: Dynamic Dashboards
What a Dynamic Dashboard Is
Every dashboard has a running user, the user whose record access and sharing rules determine the data shown in the components. A standard (static) dashboard has a single fixed running user; everyone who can access the dashboard folder sees exactly the same numbers, calculated as if they were that user. A dynamic dashboard instead sets the running user to the dashboard viewer (in Setup language, View dashboard as: The dashboard viewer). Each person who opens the dashboard sees only the records that their own profile, role, sharing rules and field-level security allow them to see.
The Three Running User Options
When you edit dashboard properties you choose one of the following:
1. Me (a specific named user, typically the creator): a static dashboard. All viewers see data as this user. This is the option that can accidentally over-expose data if the running user has broad access and the dashboard folder is widely shared.
2. Another person: still static, but the running user is someone else, for example a VP of Sales. You can also tick Let dashboard viewers choose whom they view the dashboard as, which allows users with the View My Team's Dashboards or View All Data permission to switch the running user to a subordinate.
3. The dashboard viewer: this is the dynamic dashboard. The logged-in user is always the running user.
How It Works
When a dynamic dashboard is opened, Salesforce runs the underlying source reports in the context of the viewer. Role hierarchy, sharing rules, organization-wide defaults, manual shares and team membership are all respected. A sales rep sees only their own opportunities, their manager sees the whole team, and the VP sees the entire region, all from one dashboard with one set of components. Because the data is calculated at view time for each individual, a dynamic dashboard cannot have a single cached snapshot shared by everyone, which drives several of its restrictions.
Key Limits and Restrictions You Must Memorize
- Number per org: Enterprise Edition allows up to 5 dynamic dashboards, Unlimited and Performance Editions allow up to 10, and Developer Edition allows up to 3. Additional dynamic dashboards can be purchased from Salesforce. The limit is on dynamic dashboards only; static dashboards are not counted.
- No scheduled refresh: Dynamic dashboards cannot be scheduled to refresh and cannot be subscribed to for emailed snapshots. They must be refreshed manually when viewed, because there is no single running user whose data could be sent.
- No private folders: A dynamic dashboard cannot be saved to a user's private dashboards folder; it must live in a shared folder.
- Permission to create: The Manage Dynamic Dashboards permission is required to create, edit or delete a dynamic dashboard. To set the running user to another specific person you need View All Data, or View My Team's Dashboards if that person is below you in the role hierarchy.
- Chatter and following: In Salesforce Classic, dashboard components on dynamic dashboards cannot be followed or posted as snapshots to Chatter in the same way as static components, because the values differ per user.
- Folder access still matters: A dynamic dashboard controls what data a viewer sees, but folder sharing controls whether they can open the dashboard at all. You still need to share the folder appropriately.
When to Recommend a Dynamic Dashboard
Choose a dynamic dashboard when the requirement is that different users should see different data from the same layout, driven by their own record access. Typical phrasing in a scenario: each sales rep should see only their own pipeline, managers should see their team, and the company wants to avoid creating one dashboard per rep. A dynamic dashboard is also the secure choice when a static running user would reveal records a viewer is not normally allowed to see.
Part 2: Dashboard Filters
What a Dashboard Filter Is
A dashboard filter is a picklist-style control at the top of a dashboard that lets a viewer narrow every component at once by a chosen field value, for example Region equals West, or Close Date equals This Quarter. Instead of cloning a dashboard for each region, product line or fiscal period, you build one dashboard and let users apply filters interactively. Filters change the slice of data displayed; they do not change the security context, so they are often combined with a dynamic dashboard to get both personalization and interactivity.
How Dashboard Filters Work
- You add filters in the dashboard editor by selecting a field. In Lightning Experience you pick the field from one of the source reports and Salesforce automatically maps equivalent fields on the other components' source reports (for example, Account Industry on an Opportunity report and Industry on an Account report).
- You then define the filter values (also called filter options). Each value has an operator and a value, such as equals, not equal to, greater than, less than, contains, starts with, or for dates, relative values like LAST QUARTER or THIS YEAR. You can group multiple criteria into a single option, for example a single option named Enterprise that means Annual Revenue greater than 10,000,000 OR Number of Employees greater than 1,000.
- When a viewer selects a value, every component whose source report contains the filter field is re-run with that condition appended. Components whose source report does not include the field are not filtered and continue to show unfiltered results; the editor warns you about this when you set the filter up.
- When a user drills from a filtered component into the source report in Lightning Experience, the dashboard filter is carried into the report view so the numbers match.
- The last-used filter selection is remembered for the user when they return to the dashboard.
Key Limits and Restrictions You Must Memorize
- A dashboard can have up to 3 filters.
- Each filter can have up to 50 filter values (options).
- Filters apply only to report-based components; they are not applied to Visualforce components or custom s-controls.
- Filter fields must exist on (or be equivalent to a field on) the source reports. If the field is missing from a report, that component is unaffected.
- Bucket fields cannot be used as dashboard filter fields; bucket fields exist only within a report. The workaround is to recreate the grouping logic as a filter option with multiple criteria, or to use a formula field on the object.
- Filters are not applied to scheduled refreshes or subscription emails; the emailed or refreshed snapshot always reflects the unfiltered dashboard.
- Filters work on standard and custom fields of most types: picklist, text, lookup/ID, number, currency, checkbox and date/datetime.
- Dashboard filters do not override sharing or field-level security; they only narrow what the running user can already see.
When to Recommend Dashboard Filters
Choose filters when the requirement is that the same user wants to toggle between views of the data, for example switching between regions, product families or time periods, or when the org wants to reduce dashboard sprawl without needing per-user security. Filters are also the right answer when an org has already used up its dynamic dashboard allocation and needs flexibility without purchasing more.
Part 3: Dynamic Dashboards versus Dashboard Filters
Purpose: Dynamic dashboards personalize security context (what each person is allowed to see). Filters personalize scope (which subset a person chooses to look at).
Who controls the view: Dynamic dashboards are automatic based on login; filters are chosen manually by the viewer.
Scheduling: Static dashboards with filters can be scheduled and subscribed to (unfiltered); dynamic dashboards cannot be scheduled at all.
Limits: 5/10/3 dynamic dashboards per edition versus 3 filters and 50 values per filter on any dashboard.
Combination: A dynamic dashboard can also have filters. Example: a single Sales Performance dashboard where each rep sees only their own records (dynamic) and can switch between This Quarter and Last Quarter (filter).
Part 4: Common Scenario Patterns and the Correct Answers
Scenario: A company with 200 sales reps wants each rep to see a dashboard showing only their own opportunities without the admin building 200 dashboards. Answer: Create one dynamic dashboard with the running user set to the dashboard viewer and share the folder with the sales profile.
Scenario: The regional VP wants to open the sales dashboard and switch between the North, South, East and West regions. Answer: Add a dashboard filter on the Region field with one filter value per region.
Scenario: An Enterprise Edition org tries to create a sixth dynamic dashboard and receives an error. Answer: The org has hit the limit of 5 dynamic dashboards; either convert an existing one to static, use dashboard filters on a static dashboard, or purchase additional dynamic dashboards.
Scenario: Management wants a dynamic dashboard emailed to all managers every Monday morning. Answer: Not possible; dynamic dashboards cannot be scheduled or subscribed to. Recommend a static dashboard with an appropriate running user, or have managers refresh manually.
Scenario: A filter on Industry applies to four components but one component still shows all records. Answer: The source report for that component does not contain the Industry field or an equivalent field; add the field to the report or accept that the component is unfiltered.
Scenario: A user needs to add a fourth filter for Product Family. Answer: Cannot be done; the maximum is 3 filters. Consider combining criteria into a single filter option, creating a separate dashboard, or using a dynamic dashboard to reduce the need for one of the existing filters.
Scenario: An administrator cannot find the option to set the running user to the dashboard viewer. Answer: The admin lacks the Manage Dynamic Dashboards permission, or the dashboard is in a private folder.
Scenario: A dashboard with the running user set to the CEO is shared with all internal users and reps are now seeing confidential deals. Answer: This is a data exposure caused by a static running user; convert it to a dynamic dashboard or change the running user and restrict folder access.
Scenario: A user wants to filter a dashboard on a bucket field they created in a report. Answer: Bucket fields cannot be dashboard filter fields; create a formula field on the object or build a multi-criteria filter option.
Exam Tips: Answering Questions on Dynamic Dashboards and Dashboard Filters
1. Decode the keywords. Phrases such as each user should see only their own data, based on their role, without creating a dashboard for each person or respect sharing settings point to a dynamic dashboard. Phrases such as switch between, toggle, select a region or period, same user wants different views point to dashboard filters.
2. Memorize the numbers. Dynamic dashboards: 5 in Enterprise, 10 in Unlimited and Performance, 3 in Developer. Filters: 3 per dashboard, 50 values per filter. Numeric limits are among the easiest points to win or lose.
3. Remember what cannot be done. Dynamic dashboards cannot be scheduled, subscribed to, or saved in private folders. Filters cannot be applied to Visualforce components, bucket fields, or to scheduled and emailed snapshots. If an answer option proposes one of these, it is usually a distractor.
4. Know the permissions. Manage Dynamic Dashboards to create them; View All Data or View My Team's Dashboards to set another person as running user or to let viewers choose the running user. Questions about a missing option are often really permission questions.
5. Separate data access from dashboard access. The running user governs what data appears; folder sharing governs who can open the dashboard. A correct answer often involves both, for example create a dynamic dashboard and share the folder with the relevant public group.
6. Watch for data exposure traps. If a scenario describes users seeing more data than they should, suspect a static running user with broad access combined with wide folder sharing. The fix is a dynamic dashboard or a more appropriate running user, not a sharing rule change.
7. Check the source reports when a filter misbehaves. A filter that does not affect one component almost always means the filter field is missing from that component's source report. Equivalent field mapping only works when the field exists.
8. Consider combining both features. When a scenario asks for personalized security plus interactive slicing, the best answer is a dynamic dashboard with filters, not one or the other.
9. Eliminate overbuilt answers. Options suggesting one dashboard per user, per region or per period, or custom code such as Visualforce or Apex, are rarely correct when a dynamic dashboard or a filter solves the problem declaratively with less maintenance.
10. Think like a consultant. The Advanced Administrator exam rewards solutions that are scalable, secure and low-maintenance. When two options both technically work, pick the one that reduces the number of dashboards, respects existing sharing and stays within org limits.
Quick Reference Summary
- Dynamic dashboard = running user is the dashboard viewer; data reflects each viewer's own access.
- Requires Manage Dynamic Dashboards; must be in a shared folder; cannot be scheduled or subscribed.
- Limits: 5 (Enterprise), 10 (Unlimited/Performance), 3 (Developer); more can be purchased.
- Dashboard filter = up to 3 per dashboard, up to 50 values each, applies to components whose source report has the field or an equivalent.
- Filters do not apply to Visualforce components, bucket fields, or scheduled/emailed dashboards, and never override sharing.
- Use dynamic dashboards for who sees what; use filters for which slice to view; combine them for both.
Test mode:
Admin II - Dynamic Dashboards and Dashboard Filters Example Questions
Test your knowledge of Dynamic Dashboards and Dashboard Filters
Question 1
Northern Trail Outfitters wants one pipeline dashboard for its regional sales managers. Each manager must see only the opportunities their team can access, and must be able to switch the view between product families. The Opportunity org-wide default is Private, and the role hierarchy mirrors the sales regions. The administrator's first draft runs the dashboard as the sales director and adds a Region filter. Which recommendation best meets the requirements?
Question 2
Cloud Kicks has a dashboard that runs as the logged-in viewer. The administrator also turned on the setting that lets viewers choose whom they view the dashboard as. Sales directors have a profile cloned from Standard User and Viewer access to the dashboard folder. They report that they still only see their own data and cannot switch the view to the reps below them in the role hierarchy. What should the administrator do to meet the requirement while granting the least access?
Question 3
Universal Containers sets the Opportunity org-wide default to Private. The administrator is building one pipeline dashboard. Each sales rep must see only the opportunities they can access. Sales managers must also be able to view the same dashboard as any rep who reports to them in the role hierarchy. Which configuration meets these requirements while granting the least access?
Unlock Premium Access
Salesforce Certified Platform Administrator II
- Access to ALL Certifications: Study for any certification on our platform with one subscription
- 2973 Superior-grade Salesforce Certified Platform Administrator II practice questions
- Unlimited practice tests across all certifications
- Detailed explanations for every question
- Admin II: 5 full exams plus all other certification exams
- 30-Day Money-Back Guarantee: Full refund within 30 days if unsatisfied
- Risk-Free: 7-day free trial with all premium features!
More Dynamic Dashboards and Dashboard Filters questions
24 questions (total)
Other Data and Analytics Management concepts
Backup, Restore and Data Export OptionsBig ObjectsBucket FieldsCross Filters and Filter LogicCustom Report TypesCustom Summary Formulas and Row-Level FormulasData Enrichment and Data Archiving StrategyData Import Wizard Versus Data LoaderData Types and Field Choice for Data QualityExternal IDs and UpsertJoined ReportsMatching Rules and Duplicate RulesReporting SnapshotsSalesforce Connect and External ObjectsValidation Rules for Data Quality