7 Salesforce dashboard checks for more trustworthy reporting

Salesforce dashboards are designed to make information easy to absorb. That convenience can also hide the questions that matter most: which records are included, whose access controls the results, when the figures were refreshed and whether the underlying data means what the chart title suggests.

You do not need a reporting transformation project to make a dashboard more dependable. A short, repeatable review can catch many of the issues that cause teams to debate numbers in meetings or return to spreadsheets. Here are seven checks that admins, managers and everyday dashboard users can apply.

1. Write down the question each metric should answer

For managers: begin with the decision, not the chart type. “Open pipeline” might mean every opportunity that is not closed, opportunities expected this quarter, or only deals above an agreed confidence level. Those are different measures.

Give important metrics a short definition covering the object, date field, population and exclusions. Then compare that definition with the source report. This is an Ostrelis recommendation rather than a Salesforce product requirement, but it prevents a technically correct report from answering the wrong business question.

Quick action: choose one heavily used dashboard and ask its owner to explain each metric in a sentence. If the audience cannot agree on the sentence, fix the definition before redesigning the chart.

2. Review the source-report filters

For admins: open each source report and inspect the standard filters, field filters and filter logic. Salesforce Trailhead explains that standard filters such as Show Me and date range operate alongside field filters, while Boolean filter logic applies only to field filters. A single unexpected “My records” setting or an old fixed date can materially change the result.

Pay particular attention to which date field is selected. Created Date, Close Date and Last Activity Date answer different questions. Relative dates such as THIS MONTH or LAST 90 DAYS can keep recurring reports useful, but only when they match the agreed metric.

Quick action: record the intended filters in the report description so the next person can distinguish deliberate logic from an accidental setting.

3. Confirm whose view controls the dashboard

For admins and users: check the dashboard’s “View Dashboard As” setting. A dashboard with a fixed running user can show viewers data according to that user’s access. Salesforce confirms that a dynamic dashboard instead shows each viewer only data they can access.

Neither option is automatically better. A leadership dashboard may need a consistent organisation-wide view, while a team dashboard may be more useful when every person sees their own permitted records. Confusion starts when the audience assumes one behaviour and the dashboard uses the other.

Quick action: test the dashboard as two representative users. Explain the viewing basis near the dashboard or in its description if different results are expected.

4. Check when the data was last refreshed

For users: look at the Last Refreshed information before using the figures in a meeting or operational decision. Salesforce Help confirms that refreshing a dashboard updates its results for users with access. It also notes an easy-to-miss mobile detail: pulling down to refresh the Salesforce mobile app does not refresh dashboard data; use the dashboard’s Refresh action.

A recent timestamp does not guarantee good source data, but an old timestamp is a clear reason to pause. Agree a refresh expectation that matches how often the underlying process changes.

Quick action: add “check refresh time” to the agenda template for recurring dashboard reviews rather than assuming the numbers are live.

5. Test totals against real records and edge cases

For admins: sample a few records that should appear and a few that should not. Include records with blank values, boundary dates, changed owners and unusual statuses. Drill into a dashboard component where available and compare the total with the source report.

This is practical quality assurance, not a Salesforce feature. It catches problems that visual inspection will not: incomplete data, misunderstood stage values, duplicate records or a formula that handles blanks unexpectedly.

Quick action: keep three to five representative test scenarios with the dashboard’s maintenance notes and rerun them after filter, field or automation changes.

6. Review folder access and dashboard filters

For admins: confirm that the right users can access both the dashboard folder and its supporting reports. Access problems often look like reporting problems when a colleague cannot open a drill-down or receives a different result.

Dashboard filters can reduce duplicate dashboards by letting viewers choose a region, team or other perspective. Salesforce Help confirms that the selected filtered view is remembered for the next visit. That is convenient, but it means two people discussing “the dashboard” may have different filters applied.

For users: say which filter view you are using when sharing a figure or screenshot. For admins: give filters clear labels and sensible values, then test their effect across every component.

7. Check subscriptions as a separate experience

For admins and managers: a dashboard email is not identical to the interactive dashboard. Salesforce documents several subscription limitations: dashboard filters are not applied to emailed dashboards, dynamic dashboards cannot be subscribed to, and recipients need access to the containing folder.

Subscriptions are still useful for bringing information into a regular routine, but test the email that recipients actually receive. Make sure its unfiltered view is appropriate and that the message does not invite a conclusion that requires the interactive context.

Quick action: review active subscriptions when an owner changes or a dashboard is redesigned. Remove obsolete deliveries and ask recipients whether the email still helps them act.

A small monthly habit

These checks work best as a light maintenance routine rather than a one-off audit. Review the busiest dashboards first, assign an owner and note the metric definitions, source reports, viewing basis and expected refresh pattern. When a business process or important field changes, repeat the relevant checks.

Ostrelis can help teams clarify reporting questions, improve source data and maintain dashboards that support real operational decisions. See our Salesforce reporting and dashboard services, Salesforce administration support and practical Salesforce health check.