Skip to content
Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionarySSummary Report
AnalyticsIntermediate

Summary Report

A Summary Report is one of the four Salesforce report formats.

§ 01

Definition

A Summary Report is one of the four Salesforce report formats. It groups rows of data by the values in one or more fields, then calculates subtotals for each group and a grand total for the whole report. You pick the format in the report builder, alongside Tabular, Matrix, and Joined.

The format answers questions that involve "how much" or "how many" broken down by a category. Think pipeline by stage, cases by status, or opportunity amount by owner. A Summary Report sits one step above a plain list, because it adds grouping and aggregation while still showing the underlying detail rows.

§ 02

How Summary Reports group, subtotal, and chart your data

Where it fits among the four report formats

Salesforce reports come in four formats: Tabular, Summary, Matrix, and Joined. Tabular is the default and the simplest. It lists matching records as rows with fields as columns, much like a spreadsheet, and it shows a single grand total at the bottom. Tabular cannot group rows or build a chart. Summary is the next step up. The official help describes it as letting you "group rows of data, view subtotals, and create charts." Matrix goes further by grouping records both by row and by column at the same time, which suits side-by-side comparisons across two dimensions. Joined lets you place several report blocks next to each other, each with its own view, and can combine different report types. Most reporting questions involve grouping by one or two fields and totaling a number. That is exactly what Summary covers, which is why it is the format admins reach for most often. You start in Tabular and switch to Summary the moment you drop a field into a grouping zone. The builder converts the report and begins showing subtotals.

Grouping rows, and grouping by date

Grouping is the heart of a Summary Report. You add a group by dropping a field onto the grouping drop zone, or by opening a column menu and choosing Group by this Field. A Summary Report supports up to three grouping levels, so you can nest groups inside groups. For example, group opportunities by owner, then by stage, then by product family. Each level rolls up into the one above it. Salesforce treats date fields with extra care. When you group by a date field, you can open the group menu, select Group Dates By, and pick a time frame: day, week, month, quarter, or year. That single setting turns a flat list of dated records into a clean monthly or quarterly breakdown without any formula work. Grouping is also what makes a report chartable and dashboard-ready. A Summary Report with no groupings behaves almost like a Tabular report, so the value really comes from choosing the right fields to group on. Pick fields with a manageable number of distinct values, because grouping on something high-cardinality like a free-text field produces a long, hard-to-read result.

Subtotals, grand totals, and the four summaries

Once rows are grouped, you summarize numeric columns to get the totals. Salesforce offers four summary types: Sum, Average, Max, and Min. The documentation states that "Summaries calculate subtotals for every group in a report, as well as a grand total for all report data." So a single summary appears in three places. It shows as a subtotal under each group, as a grand total at the bottom, and at the top of the run page for quick reference. You can apply more than one summary to the same field, and in fact you can apply all four at once. To add one, open the menu next to a numeric column and choose Summarize, then pick the calculation. A worked example helps. Suppose you group closed-won opportunities by owner and summarize Amount by Sum. Each owner block now ends with that rep's total bookings, and the grand total shows the team number. Add an Average and you also see the typical deal size per rep. The detail rows stay visible underneath, so you keep both the totals and the records that produced them.

Custom summary formulas for calculated totals

The four built-in summaries cover the common cases, but they only add, average, or find extremes of a single column. When you need a calculation across summarized values, you reach for a custom summary formula. This is a formula column that runs at the subtotal and grand-total levels rather than on each row. A classic use is a win rate. You divide the count of won opportunities by the total count, then format the result as a percent, and the figure recalculates correctly for every group and the grand total. Custom summary formulas let you choose which grouping levels they apply to, and whether they calculate at the grand total. Selecting All summary levels shows the result at every group and the grand total. Because these formulas operate on aggregated data, they can reference the report's summaries, not raw field values. That distinction trips up new report builders who expect row-level formula behavior. Custom summary formulas only exist in Summary, Matrix, and Joined formats, which is one more reason to choose Summary over Tabular when calculations on grouped data matter.

Charts, dashboards, and conditional highlighting

A Summary Report can carry a chart, which Tabular cannot. The chart sits at the top of the report and visualizes the grouped subtotals as bars, lines, donuts, or other types. This matters beyond the report page itself, because dashboard components draw their data from a source report. A grouped Summary Report is one of the most natural sources for a dashboard chart or gauge, since the groupings map directly to the categories on the component. Summary Reports also support conditional highlighting, where you color subtotal cells based on thresholds you set, for instance green above target and red below. That turns a wall of numbers into something a manager can scan in seconds. When you build for a dashboard, keep the grouping aligned with what the component needs, because the first grouping usually becomes the axis or the segments. A well-structured Summary Report can feed several dashboard components at once, which keeps your reporting library smaller and easier to maintain. The combination of grouping, subtotals, charts, and highlighting is what makes this format the everyday workhorse of Salesforce analytics.

Choosing Summary over the other formats

Picking a format is mostly about the shape of the question. Choose Tabular when you just need a list to export or scan, with no grouping. Choose Summary when you want grouped totals along one dimension, which is the majority of analytical reports. Choose Matrix when you need a grid that totals across two dimensions at once, such as product family down the side and quarter across the top. Choose Joined when you want to compare blocks from different report types side by side. Switching formats is easy and non-destructive in the builder, so you can start in Summary and try Matrix if a second dimension appears. Keep in mind the grouping ceilings: Summary and Joined allow up to three groupings, while Matrix allows two row and two column groupings and forbids reusing the same field on both axes. If a report grows past three meaningful groupings, that is usually a sign to split it or rethink the question. For most pipeline, activity, and case reports, Summary gives you the grouped subtotals and chart support you need without the extra setup that Matrix demands.

§ 03

Build a Summary Report in the report builder

Here is how to build a Summary Report in the Lightning report builder. The same idea applies in Salesforce Classic, with slightly different menu wording.

  1. Create a new report and pick a report type

    From the Reports tab, click New Report. Choose the report type that exposes the object and fields you want, for example Opportunities. The report type decides which fields are available, so pick it carefully.

  2. Add a grouping to switch into Summary format

    In the builder, drag a field such as Stage or Owner into the Group Rows zone, or use the column menu and choose Group by this Field. Adding the first grouping turns a Tabular report into a Summary report automatically.

  3. Summarize one or more numeric columns

    Open the menu next to a number field like Amount and choose Summarize, then select Sum, Average, Max, or Min. The subtotal appears under each group and as a grand total at the bottom.

  4. Add a chart and run the report

    Click Add Chart to visualize the grouped subtotals, adjust the chart type, then click Run. Save the report into a folder so it can feed a dashboard later.

Report Typerequired

The template that defines which object and related fields the report can use. Chosen first and not changeable afterward.

Grouping fieldrequired

At least one row grouping is what makes the report a Summary. Without a grouping it stays Tabular.

Summarized fieldrequired

A numeric column with a Sum, Average, Max, or Min applied, so the report produces subtotals and a grand total.

Gotchas
  • A Summary Report with zero groupings looks and behaves like a Tabular report. The grouping is what defines the format.
  • You can nest at most three row groupings. If you need more breakdowns, consider a Matrix report or splitting the report.
  • Custom summary formulas run on summarized data, not on each row, so they cannot reference raw field values the way row-level formulas do.
§

Trust & references

Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on Summary Report.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.

§

Test your knowledge

Q1. What is a Summary Report?

Q2. How many grouping levels?

Q3. When use summary vs tabular?

§

Discussion

Loading…

Loading discussion…