Section 5 · Reporting · 15% of exam
5.1 Report Purpose, Formats, and Filters
Exam objective
Explain how dashboards summarize report data and how dashboard context affects what users see.
https://help.salesforce.com/s/articleView?id=analytics.analytics_overview.htm&language=en_US https://trailhead.salesforce.com/content/learn/modules/cert-prep-salesforce-certified-associate/review-reports-and-dashboards https://help.salesforce.com/s/articleView?id=xcloud.basics_organize_data.htm&language=en_US&type=5
Core concepts
A dashboard presents visual summaries using components such as charts, tables, metrics, or gauges. Each component is based on a source report. A report is the underlying dataset and filter logic; a dashboard arranges selected results to help a reader monitor performance or investigate a trend. A dashboard should make a small number of important questions easy to answer, not reproduce every detail from every report.
Example: A service leader wants to see unassigned Cases, Cases by priority, and average age of open Cases. The source reports should use consistent definitions of “open,” “unassigned,” and the age period. The dashboard can display a metric for the total, a chart by priority, and a table of oldest cases. Clicking through to the source report should support investigation of the summarized value.
Dashboard data context matters. A dynamic dashboard can show data as the logged-in viewer, subject to features and limits. A dashboard with a specified running user can present data visible to that user, which may differ from each viewer’s own record access. The precise behavior depends on dashboard settings and permissions. Administrators should consider whether users should see a shared management view or only the records they can access individually. Filters can help a dashboard serve multiple audiences without creating many copies. For example, a region filter can let a manager switch between territories. However, a filter is not a security control. It narrows what the component displays but does not replace permissions or sharing. Avoid presenting confidential information simply because a dashboard filter currently hides it.
If a dashboard component displays unexpected values, check its source report, filters, grouping, refresh state, dashboard filter selection, and running-user context. A dashboard is a visualization of source data and security context; it is not an independent database. Fixing the chart type will not resolve a source report that omits records.
Dashboard and report folder access determines who can locate or manage those analytics assets; record access still governs the data returned.
A dashboard communicates the headline; the report supports the detail. Follow the metric back to its source when validating an unexpected result.
Extra concept
Extra concept: A snapshot or historical trending feature, where available and configured, can preserve measurements over time. A normal report usually reflects the records at the time it runs rather than a complete historical series.
Key takeaways
- A dashboard presents visual summaries using components such as charts, tables, metrics, or gauges.
- Example: A service leader wants to see unassigned Cases, Cases by priority, and average age of open Cases.
- Dashboard data context matters.
- Official references: https://help.salesforce.com/s/articleView?id=analytics.analytics_overview.htm&language=en_US https://help.salesforce.com/s/articleView?id=sf.security_overview.htm&language=en_US&type=5 https://trailhead.salesforce.com/content/learn/modules/cert-prep-salesforce-certified-associate/review-reports-and-dashboards
