Report
A Report in Salesforce is a saved query against the platform's data, with filters, groupings, summaries, and a chosen layout.
Definition
A Report in Salesforce is a saved query against the platform's data, with filters, groupings, summaries, and a chosen layout. Reports answer questions like "how many open opportunities over $50,000 close this quarter?" or "which support agents have the longest average case resolution time?" They are the foundation of every dashboard component, the source for many exports and integrations, and the most-used analytical tool in any Salesforce org.
Every report is built on a Report Type, which defines the objects, relationships, and fields available. Filters narrow the row set. Groupings collapse rows into summary buckets. Summary formulas compute derived metrics within groups. The four format variants (Tabular, Summary, Matrix, Joined) shape how groupings and summaries render. Report Builder in Lightning Experience is the modern construction surface, with drag-and-drop column reordering, inline filtering, and live preview. Reports save to folders, and folder access controls who can view, edit, and share each report.
How reports turn Salesforce data into answers
Report Types and the data model behind reports
Every report starts from a Report Type, either a standard one shipped by Salesforce (Opportunities with Products, Accounts with Contacts) or a custom Report Type built in Setup. The Report Type defines the primary object, the related objects joined to it, and the fields exposed for filtering and grouping. Choosing the right Report Type is the single most important design decision because it constrains every other choice. Custom Report Types are necessary for reports that span objects in non-standard ways, like Opportunities without Activities or Accounts with Cases joined through a custom lookup.
Four formats: Tabular, Summary, Matrix, Joined
Tabular reports show rows as a flat list, like a spreadsheet. Summary reports group rows by one or more fields and show subtotals per group. Matrix reports cross-tabulate two grouping axes, like a pivot table. Joined reports combine multiple report blocks side-by-side for cross-report comparisons. Each format has different layout, calculation, and chart capabilities. Tabular is the right pick for raw data exports; Summary is the most common for operational reports; Matrix fits cross-segment analysis; Joined fits comparing data sets that share a common field.
Filters, cross-filters, and filter logic
Filters narrow which records appear in the report. Standard field filters compare a field to a value with operators like equals, contains, greater than. Cross-filters filter the primary object by the presence or absence of related records (Accounts with Cases, Accounts without Opportunities). Filter logic lets you combine filters with AND/OR/NOT, useful for "matches criteria A or both B and C" patterns. Effective filter design keeps reports fast and accurate; sloppy filtering produces inflated row counts that hit the 2,000-row preview limit.
Groupings, subtotals, and summary formulas
Summary and Matrix reports collapse rows into groups via Group Rows or Group Columns settings. Each group can show count, sum, average, min, max for numeric fields automatically. Summary formulas (Add Formula > Summary Formula) compute custom aggregations: percentage of total, year-over-year delta, weighted averages. Bucket fields let you create ad-hoc categorizations directly in the report without modifying the underlying data. These features are what turn raw row counts into actionable metrics.
Charts, conditional highlighting, and visualization
Each report can have one chart that summarizes its data, displayed alongside the row results. Chart types include bar, column, donut, line, scatter, funnel, and combination. Conditional highlighting colors values based on thresholds (red below target, green above). Chart and highlighting choices should reinforce the question the report answers; mismatched visualizations confuse rather than inform. Reports embedded in dashboards use a different visualization picked per dashboard component, so the report-level chart is optional.
Row limits, schedule, and export
Reports cap at 2,000 rows in the in-Salesforce preview and 50,000 rows for export. Larger result sets need pagination, Bulk API queries, or CRM Analytics. Reports can be subscribed to (email-delivered to recipients on a schedule) or exported manually to Excel or CSV. Scheduled reports run in the background; the recipient receives a formatted email with the report attached or linked. Export formats include Formatted (preserves Excel formulas) and Details Only (raw values).
Folder access and sharing
Each report saves to a Report Folder. The folder access settings (Viewer, Editor, Manager) control who can see, modify, and share the report. Personal folders are visible only to the owner; shared folders propagate access through the platform sharing model. Plan folder structure before building many reports because reorganizing after the fact is tedious. Most production orgs use a folder per team or function, with role-based sharing rules at the folder level.
How to build a Report
Building a useful report takes deliberate design, not just clicking through the wizard. Pick the right Report Type, set focused filters, choose the format that fits the analytical question, group meaningfully, and verify the numbers against a known reference. The best reports answer one specific question cleanly rather than displaying every possible column.
- Identify the question the report answers
State the question in one sentence. "Which open opportunities owned by my team close this quarter?" beats "Show opportunity data." The question shapes the Report Type, filters, groupings, and chart choices.
- Pick the Report Type
App Launcher > Reports > New Report. Pick a Report Type that includes the primary object and any related objects needed. Use standard Report Types when they fit; build custom Report Types for cross-object analysis the standard ones do not support.
- Add and configure filters
Filters panel > add filters for the time range, ownership, stage, status, or whatever narrows the data to the question. Use cross-filters for records that need a related record (Accounts with Opportunities) or the absence of one (Accounts without Activities in the last 30 days).
- Choose the format and add groupings
Tabular for flat exports. Summary for grouped totals. Matrix for cross-tabs. Joined for multi-block comparisons. Add Group Rows and Group Columns based on the question. Each grouping produces subtotals automatically.
- Select columns and reorder them
Drag fields from the Fields panel onto the report. Reorder columns by dragging headers. Remove columns that do not help answer the question; clutter reduces readability and slows the report.
- Add summary formulas and bucket fields
Add Formula for derived metrics: percentage of total, win rate, average deal size. Bucket fields for ad-hoc categorization without modifying the underlying data: bucket Amount into Small, Medium, Large ranges.
- Add a chart and conditional highlighting
Chart icon > pick a chart type and configure axes. Conditional Highlighting > set thresholds for color coding. The chart and highlighting should reinforce the question being asked.
- Save to the right folder and configure sharing
Save the report to a folder that matches its audience. Confirm folder sharing covers the right users. Test by logging in as a representative user to verify they can see it and the data matches expectation.
Defines which objects, relationships, and fields are available. The foundational design choice that constrains every other option.
Tabular, Summary, Matrix, or Joined. Determines how groupings and summaries render and which chart types are available.
Combines filters with AND, OR, and NOT operators. Default is AND across all filters; custom logic lets you build complex criteria.
- Reports cap at 2,000 rows in the preview and 50,000 rows for export. Larger result sets need pagination, Bulk API queries, or CRM Analytics.
- Report Type choice constrains every other report option. Picking the wrong Report Type means rebuilding the report from scratch because the field list cannot be expanded mid-build.
- Filters on non-indexed fields with high cardinality can time out on large objects. Use indexed fields (Id, Name, Owner, External ID) wherever possible for fast filter evaluation.
- Cross-filters are powerful but expensive on large data sets. Each cross-filter adds a sub-query; multiple cross-filters can produce queries that exceed report timeout limits.
- Folder access controls report visibility. Saving a report to the wrong folder either hides it from the intended audience or exposes it to people who should not see it.
Trust & references
Cross-checked against the following references.
- Reports OverviewSalesforce Help
- Report BuilderSalesforce Help
- Report FiltersSalesforce Help
Straight from the source - Salesforce's reference material on Report.
- Filter Report DataSalesforce Help
- Group Report DataSalesforce Help
- Charts in ReportsSalesforce Help
Hands-on resources to go deeper on Report.
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 type of data does Report typically work with?
Q2. How can Report help improve sales performance?
Q3. What is the primary purpose of Report in Salesforce?
Discussion
Loading discussion…