You can spend weeks building beautiful objects, clean fields, and careful automation — and none of it matters to the person at the top if they can’t see what’s going on. “How many deals closed this month? Which rep is ahead? Are cases piling up?” Those questions are answered by two of the most underrated tools in Salesforce: reports and dashboards. They need no code, and yet they’re often what makes leadership actually trust the system you built.
Let me walk you through them the way I’d introduce them to someone on their first week.
The difference in one breath
People mix these two up constantly, so let’s settle it immediately:
- A report is a list of records that answer a question, organised so you can read it — “all Opportunities closing this quarter, grouped by owner.”
- A dashboard is a visual summary built from reports — the charts, gauges, and numbers on a single screen that someone glances at over morning coffee.
A report is the question answered in rows and columns. A dashboard is several of those answers turned into a picture you can read in five seconds. You build reports first; dashboards stand on top of them.
That dependency is the key beginner insight: a dashboard chart always sits on a report underneath it. No report, no chart. So everything starts with reports.
The building blocks of a report
Every Salesforce report is assembled from a few simple parts. Understand these four and you can build almost anything:
1. The report type — what data you’re allowed to see
Before you pick anything, you choose a report type: it decides which object you’re reporting on and which related data is available — “Opportunities,” or “Opportunities with Products,” or “Cases with Contacts.” It’s the lens. Pick the wrong one and the fields you need simply won’t be there, which trips up nearly every beginner at least once.
2. Filters — which records count
Filters narrow the records down to the ones that matter: “Close Date this quarter,” “Stage = Closed Won,” “Country = Germany.” This is the same filtering instinct you’d use on a spreadsheet — keep only the rows that answer your question.
3. Grouping — how the data is organised
Grouping is where a flat list becomes insight. Group Opportunities by Owner and you instantly see each rep’s deals together with a subtotal. Group by Stage and you see your pipeline shape. Grouping turns “300 rows” into “here’s the pattern.”
4. Summaries — the numbers that matter
Finally, summarise: sum the Amount, count the records, average the deal size. A grouped, summarised report is the difference between a data dump and an answer.
Report formats, briefly
You’ll meet a few report formats. As a beginner, just know two:
- Tabular — a plain list, like a spreadsheet. Good for simple exports.
- Summary — grouped with subtotals. This is the workhorse; it’s what most useful reports are.
(There are matrix and joined reports too, but don’t reach for those until a summary report genuinely can’t answer the question. Climb only as high as you must — the same instinct from Flow, Apex, or Clicks?.)
Turning reports into a dashboard
Once you have a few good reports, a dashboard assembles them into one screen. Each dashboard component — a bar chart, a donut, a gauge, a single big metric — points at one of your reports and visualises it.
The craft of a good dashboard isn’t technical; it’s editorial. Ask: who is this for, and what decision should it help them make? A sales leader’s dashboard answers different questions than a support manager’s. A dashboard that tries to show everything ends up saying nothing. Pick the handful of numbers that actually drive a decision and show those clearly.
This is where my old profession quietly helps me. Twenty years of teaching is, in part, the craft of presenting information so a specific person actually gets it — knowing what to foreground and what to leave out. A dashboard is exactly that skill, just rendered in charts instead of a lesson.
A small warning that saves big headaches
Two traps catch nearly every beginner:
- The report type you can’t escape. If a field is missing, you almost certainly chose a report type that doesn’t include it. Don’t fight the filters — go back and change the report type.
- Dashboards only refresh when told. A dashboard shows data from the last refresh, not live. If the numbers look stale, refresh it (or set a schedule). I’ve watched people panic over “wrong” figures that were simply yesterday’s snapshot.
Your next step
Reports and dashboards are the layer where all your careful data work becomes something a human can act on — and they’re a genuinely enjoyable, no-code win to build early. To make them richer, the data underneath has to be clean and well-structured, which loops back to The Salesforce Object Model and good Validation Rules. And if you ever need to pull data in a more custom way than a report allows, that’s when SOQL steps in. Keep building through the Foundations category.