7.1 Report Types & the Four Standard Report Formats
Key Takeaways
- Report Types serve as foundational templates that determine which records, related objects, and fields are accessible within the Lightning Report Builder.
- Standard Report Types are provisioned automatically by Salesforce with predefined object relationships using inner joins, whereas Custom Report Types (CRTs) are administrator-defined templates supporting outer joins ('with or without' related records) and custom field layouts.
- Tabular reports generate row-by-row lists without groupings; they cannot display visual charts unless an explicit row limit is configured.
- Summary reports group records by rows to generate subtotals and charts; Matrix reports group records across both rows and columns in a two-dimensional grid; Joined reports combine up to five distinct blocks from different report types sharing a common grouping field.
- The Lightning Report Builder provides an interactive canvas with Outline and Filters tabs, customizable grouping tiers, and an automatic preview toggle for rapid report design.
Report Types & the Four Standard Report Formats
Quick Summary: In Salesforce, analytical reporting begins with selecting a Report Type, which acts as a foundational lens governing which objects, relationships, and fields are available for analysis. Salesforce provides out-of-the-box Standard Report Types and customizable Custom Report Types. Once a report type is chosen, data can be organized into one of four core report formats: Tabular (simple list), Summary (row groupings with subtotals and charts), Matrix (two-dimensional row and column groupings), or Joined (multi-block views across report types). Understanding when to deploy each format and how to configure them in the Lightning Report Builder is a fundamental competency on the platform.
Report Types: The Foundational Data Blueprint
Before a single row of data can be displayed or charted in Salesforce, an author must select a Report Type. A report type acts as a structural blueprint or metadata contract between the underlying database objects and the report builder interface. It determines:
- Which primary and related objects are queried.
- Which relationship join logic connects those objects.
- Which specific fields appear as available columns in the report builder field palette.
+-------------------------------------------------------------------------+
| REPORT TYPE ARCHITECTURE |
| |
| [Database Objects] ---> [Report Type Blueprint] ---> [Report] |
| (Accounts, Deals, - Object relationships - Filters |
| Cases, Custom) - Join logic (with / without) - Groupings |
| - Field layout & labels - Charts |
+-------------------------------------------------------------------------+
Standard Report Types: Out-of-the-Box Coverage
Salesforce automatically generates Standard Report Types whenever standard objects or custom objects are deployed. When an administrator creates a custom object and checks the Allow Reports checkbox, Salesforce immediately provisions standard report types for that object.
- Predefined Object Pairs: Standard report types cover common CRM relationships, such as
Accounts,Contacts & Accounts,Opportunities,Opportunities with Products, andCases with Solutions. - Inner Join Behavior: Standard report types that span two objects enforce an inner join by default. For example, selecting the standard report type
Opportunities with Productsonly returns Opportunities that have at least one associated Opportunity Product line item. Opportunities lacking products are completely excluded from the report output. - Standard Field Availability: Standard report types automatically include all standard and custom fields on the constituent objects, including standard audit timestamps and owner details.
Custom Report Types (CRTs): Tailored Data Architecture
When reporting requirements exceed the capabilities of standard report types, administrators build Custom Report Types (CRTs) in Setup > Analytics > Reports & Dashboards > Report Types. Custom report types deliver advanced administrative capabilities:
- Complex Multi-Object Hierarchies: An administrator can define an object chain starting with a primary object and attaching up to three consecutive tiers of related child objects (Object A -> Object B -> Object C -> Object D).
- Configurable Relationship Join Logic (With or Without): Unlike standard report types that require related child records, CRTs allow administrators to choose between two relationship join options at each tier:
- Inner Join (Each record must have related records): "Each 'A' record must have at least one related 'B' record." Records from Object A without child records in Object B are omitted.
- Left Outer Join ('With or Without' reporting): "'A' records may or may not have related 'B' records." This critical capability allows organizations to identify orphaned records or full customer footprints—such as generating a list of
Accounts with or without ContactsorAccounts with or without Opportunities.
- Custom Field Layout & Display Customization: Administrators can reorganize the fields available to end users:
- Add fields from related lookup objects up to 5 relationship levels away via lookup traversal (e.g., adding
Account.Owner.Departmentto a Case report). - Group fields into intuitive custom layout sections (e.g., "Executive Metrics", "Audit Timestamps").
- Rename field display labels exclusively for the report builder without altering the underlying object field metadata.
- Set default columns that automatically appear whenever a user creates a new report using that CRT.
- Add fields from related lookup objects up to 5 relationship levels away via lookup traversal (e.g., adding
- Deployment Status Control: CRTs maintain a Deployment Status toggle:
- In Development: The report type is visible and testable only by users with the Manage Custom Report Types administrative permission. Standard users cannot see or build reports from it.
- Deployed: The report type is published org-wide and accessible to all users who possess report creation privileges.
The Four Core Report Formats
Salesforce categorizes reports into four distinct structural formats based on how records are grouped, summarized, and displayed. Selecting the correct format depends directly on the analytical business question being addressed.
+--------------------+--------------------+--------------------+--------------------+
| TABULAR | SUMMARY | MATRIX | JOINED |
| (Row-by-Row List) | (Row Groupings) | (Row & Col Groups) | (Multi-Block View) |
| | | | |
| [Record 1] [Data] | [Group: North] | [Row] | [Q1] | [Q2]| [Block 1: Deals] |
| [Record 2] [Data] | Record A $100 | Tier 1| $10k | $15k| Acme $50,000 |
| [Record 3] [Data] | Record B $200 | Tier 2| $20k | $25k| [Block 2: Cases] |
| | Subtotal: $300 | Total | $30k | $40k| Acme 2 Critical |
| - No groupings | - Up to 3 row grps | - Grid comparison | - Up to 5 blocks |
| - Row limit charts | - Direct charts | - Direct charts | - Cross-type view |
+--------------------+--------------------+--------------------+--------------------+
1. Tabular Report: The Simple Spreadsheet
A Tabular Report is the simplest report format, presenting data in a plain, row-by-row table similar to an unformatted spreadsheet.
- Grouping Mechanics: Contains zero groupings. Records appear in sequential rows based on sorting criteria.
- Summarization: Supports Grand Totals for numerical and currency columns, but cannot generate subtotals because there are no categorical groupings.
- Charting Limitations: Because there are no grouped categories to plot along an axis, a Tabular report cannot generate a native visual chart.
- The Row Limit Exception: When an author configures an explicit Row Limit filter (e.g., limiting the report to the Top 10 Accounts sorted by Annual Revenue), the report unlocks the ability to serve as a data source for a Dashboard Table or Metric component.
- Primary Use Cases: Generating contact address books, exporting raw data for external auditing, producing mailing lists, and listing newly created records during data validation.
2. Summary Report: Row-Grouped Analytics
A Summary Report organizes records into hierarchical groupings based on one or more row fields. It is the most commonly used report format across the Salesforce platform.
- Grouping Mechanics: Allows grouping records by up to 3 levels of row groupings (e.g., grouping Opportunities first by
Stage, then byOpportunity Owner, then byLead Source). - Summarization: Generates automatic subtotals, record count badges, and summary statistics (
SUM,AVERAGE,MIN,MAX) for each group level, alongside overall Grand Totals. - Charting Capabilities: Natively supports adding visual charts (Bar, Column, Donut, Funnel, Line, Scatter) directly within the report builder canvas without requiring a dashboard.
- Primary Use Cases: Sales pipeline reviews by stage, open customer support tickets grouped by priority and assignee, and revenue breakdowns grouped by geographic region.
3. Matrix Report: Two-Dimensional Grid Analysis
A Matrix Report groups records across both rows and columns simultaneously, formatting data into a two-dimensional grid similar to a pivot table.
- Grouping Mechanics: Requires at least one row grouping AND at least one column grouping (supporting up to 2 row groupings and 2 column groupings, with a maximum of 4 total groupings).
- Summarization: Generates subtotals across rows, subtotals down columns, and grand totals at the intersections.
- Charting Capabilities: Supports advanced multi-dimensional charts, including Stacked Bar and Clustered Column charts, where one grouping represents the primary axis and the other grouping represents the cluster series.
- Primary Use Cases: Financial trend analysis (e.g., Opportunity revenue grouped by
Stagedown rows and byClose Monthacross columns), case volume analyzed bySupport Channelacross work shifts, or resource allocation across operational departments.
4. Joined Report: Multi-Block Cross-Functional Views
A Joined Report allows an author to combine multiple distinct blocks of data into a single unified report layout, where each block acts as an independent sub-report.
- Multi-Block Architecture: Can contain up to 5 separate blocks. Each block can draw from a different report type, feature different field columns, apply independent filters, and display its own summary formulas.
- Unifying Common Grouping: To link blocks together, all blocks must share a Common Grouping Field (such as
Account Name,User ID, orCustomer Number). - Cross-Functional Visibility: Delivers holistic business insights without building separate reports. For example, a single joined report can display:
- Block 1 (Opportunities): Closed Won sales deals for each client account.
- Block 2 (Cases): Open high-priority customer support cases for the same account.
- Block 3 (Contracts): Upcoming annual service contract renewals.
- Primary Use Cases: Executive customer 360-degree audit sheets, sales representative performance scorecards combining lead conversions with closed deals, and cross-departmental operational reviews.
The Lightning Report Builder Interface
Salesforce delivers a visual, drag-and-drop authoring environment called the Lightning Report Builder. Navigating its workspace components is essential for exam readiness:
+--------------------------------------------------------------------------+
| LIGHTNING REPORT BUILDER |
| |
| [<- Back] Report Name: Open Sales Pipeline [Save] [Run] [v] |
| |
| +-----------------------+ +--------------------------------------------+ |
| | [Outline] [Filters] | | [Toggle Chart] | [*] Update Preview Auto | |
| |-----------------------| |--------------------------------------------| |
| | GROUP ROWS | | Stage | Account Name | Amount | |
| | - Stage | |--------------------------------------------| |
| | GROUP COLUMNS | | > Prospecting (3) | $45,000 | |
| | - Close Quarter | | Acme | Alpha Corp | $25,000 | |
| | COLUMNS | | Apex | Beta LLC | $20,000 | |
| | - Account Name | | > Negotiation (2) | $120,000 | |
| | - Opportunity Owner | | Global | Gamma Inc | $120,000 | |
| | - Amount | |--------------------------------------------| |
| | - Close Date | | Grand Total: (5 Records) | $165,000 | |
| +-----------------------+ +--------------------------------------------+ |
+--------------------------------------------------------------------------+
Core Workspace Components
- Outline Tab: Controls the structural anatomy of the report.
- Columns: Add, reorder, or remove field columns.
- Group Rows: Select fields to establish row groupings, converting a Tabular report into a Summary report.
- Group Columns: Select fields to establish column groupings, converting a Summary report into a Matrix report.
- Filters Tab: Defines the scope of records returned by configuring Standard Filters, Field Filters, Cross Filters, and custom boolean Filter Logic.
- Fields Side Panel: A searchable drawer listing every field made available by the chosen report type. Authors can double-click or drag fields directly into the Columns or Grouping sections.
- Update Preview Automatically Toggle: Located in the top header. When toggled ON, the canvas updates in real time whenever columns, groupings, or filters change, rendering a limited preview of rows. When working with complex reports or massive data volumes, authors can toggle this OFF to make multiple structural modifications without waiting for the preview engine to refresh after each action.
- Run vs. Save: Clicking Run executes the report against the complete database and renders full paginated results. Clicking Save persists the report metadata into a designated report folder without navigating away from the builder.
Comprehensive Comparison of Report Formats
| Technical Attribute | Tabular Report | Summary Report | Matrix Report | Joined Report |
|---|---|---|---|---|
| Row Groupings | None (0) | 1 to 3 levels | 1 to 2 levels | Up to 3 levels (common field) |
| Column Groupings | None (0) | None (0) | 1 to 2 levels | None (0) |
| Subtotals & Counts | Grand Total only | Subtotals & Counts per group | Row & Column Subtotals | Subtotals per block |
| Native Charting | Not supported (unless Row Limit set) | Fully supported (Bar, Donut, Line, etc.) | Fully supported (Stacked & Clustered) | Supported (select blocks) |
| Multiple Report Types | No | No | No | Yes (up to 5 blocks) |
| Primary Exam Use Case | Plain address lists, mailing sheets, audit exports | Pipeline by Stage, Cases by Priority | Revenue by Stage across Close Months | Customer 360 combining Deals, Cases & Contracts |
A sales operations director needs a single analytical view that compares quarterly closed revenue across two specific dimensions: Opportunity Stage down the rows and Fiscal Close Month across the columns. Which report format should the author select?
An administrator needs to create a report that lists all corporate Accounts, including accounts that currently have zero related Contacts. Standard report types only return Accounts that possess at least one Contact. How can the administrator accomplish this requirement?
A user creates a Tabular report of active customer accounts and notices that the 'Add Chart' button in the Lightning Report Builder is disabled. What is the reason for this behavior?