# Salesforce Reports: Creation, Filters, Charts and Sharing

To create a report in Salesforce, choose the correct report type, define the record population and filters, add useful columns, then save and run the result. Validate it against known records before adding charts or subscriptions. Salesforce reports become reliable when the business meaning, date range and viewer access are explicit, rather than inferred from a plausible total.

Canonical URL: https://www.martechdevs.com/blog/salesforce-reports

By [Jafrin Akter Alo](https://www.martechdevs.com/authors/jafrin-akter-alo)

Data Engineer and Co-founder at [Martechdevs](https://www.martechdevs.com) and [Growth and Analytics Partners](https://www.growthandanalytics.com)

[LinkedIn](https://linkedin.com/in/jafrinalo)

Last updated: 2026-11-15

Next step: [Salesforce workflow implementation](https://www.martechdevs.com/crm-lifecycle). Define matching, access and accepted customer outcomes.

## Salesforce report creation decisions

Define these choices before building the first report.

| Decision | Example selection | Business meaning | Validation |
| --- | --- | --- | --- |
| Report type | Opportunities | Commercial opportunities are the reporting records | Expected fields and records available |
| Record scope | All visible opportunities | Intended owner population within user access | Known owners included |
| Date field and range | Close Date, fixed calendar month | Opportunities expected to close in that period | Boundary records included or excluded correctly |
| Status | Open | Active pipeline rather than closed outcomes | Won and lost examples excluded |
| Group and measure | Opportunity Owner, sum of Amount | Open value by responsible seller | Owner subtotals reconcile to the total |

Salesforce's [Lightning Report Builder guide](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_reports_dashboards/lex_implementation_reports_dashboards_using_report_builder) separates report type, fields, filters and outline settings. Its [summary-report exercise](https://trailhead.salesforce.com/content/learn/projects/create-reports-and-dashboards-for-sales-and-marketing-managers/create-a-simple-custom-report) demonstrates opportunity filters, owner grouping and an amount sum.

A report should answer one operational question clearly. Open pipeline by owner, opportunities created this month and deals won this month describe different populations. Decide which question matters before choosing a date field or copying an existing dashboard component.

At Martechdevs, [CRM and lifecycle implementation](https://www.martechdevs.com/crm-lifecycle) includes the definitions and reconciliation needed for reporting. We connect the report to the customer records and business process behind it, then verify the result as the people who will use it.

## Access and report-type prerequisites

Confirm that the intended builder can create and customize reports and that the intended readers can run them. Salesforce's [report creation reference](https://help.salesforce.com/s/articleView?id=analytics.reports_custom.htm&language=en_US&type=5) lists the relevant permissions, including Create and Customize Reports, Report Builder and Run Reports.

The report type determines the records and fields available to the report. Start with a suitable standard type when it answers the question. A custom report type is a separate design decision, particularly when the report needs relationships among several objects.

The existing [Salesforce report-types guide](https://www.martechdevs.com/blog/salesforce-report-types) covers object relationships, missing parent records and repeated rows in depth. This guide focuses on creating, filtering, presenting and sharing the report after the required record scope is understood.

Use a sandbox or approved test sample for the first exercise. Keep real business dates and ownership intact. Changing all existing opportunity close dates to make a tutorial chart populate would damage the meaning of the records the report is supposed to explain.

## A known four-record sample

The following hypothetical fixture uses four opportunities in USD. Alex and Sam represent approved test users in the sample environment. The date range is fixed so the expected result remains reproducible.

| Opportunity | Owner | Close date | Status | Amount, USD |
| --- | --- | --- | --- | ---: |
| CRM Report Pilot North | Alex | 20 November 2026 | Open | $12,000 |
| CRM Report Pilot South | Sam | 25 November 2026 | Open | $8,000 |
| CRM Report Pilot Won | Alex | 10 November 2026 | Won | $5,000 |
| CRM Report Pilot Next Month | Sam | 5 December 2026 | Open | $7,000 |

For open opportunities closing during November, the expected result is two records and $20,000. Alex contributes $12,000 and Sam $8,000. The won opportunity is outside the status rule, and the December opportunity is outside the date rule.

Use the sample as a specification. In an actual org, retain the real opportunity identifiers and the permitted stage values that represent open and won. The fixture's names and amounts are illustrative, not a description of existing customer records or a completed Salesforce test.

## Report creation in Lightning

1. Open the Reports tab, or use the App Launcher to find Reports.
2. Select New Report.
3. Search for the Opportunities report type and select it.
4. Select Start Report to open the builder.
5. Open Filters and review the standard scope and date settings.
6. Open Outline and add the columns required for the question.
7. Save the report with a meaningful name, description and appropriate folder.
8. Run the report and compare the result with the known sample.

These steps follow the [Report Builder workflow](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_reports_dashboards/lex_implementation_reports_dashboards_using_report_builder). Available report types and fields depend on the org and the user's access. If the expected type is missing, investigate those prerequisites instead of selecting a vaguely similar type and assuming it will return the same records.

The builder preview is a limited sample. Salesforce explicitly instructs users to run the report to see the full result. [Preview and run behavior](https://trailhead.salesforce.com/content/learn/projects/create-reports-and-dashboards-for-sales-and-marketing-managers/create-a-simple-custom-report). A correct-looking preview is useful during editing, but the executed result is the evidence to reconcile.

## Filters for the sample report

Set the sample's filters deliberately. Use the standard Show Me scope that includes the intended visible opportunities, choose Close Date as the date basis and specify 1 November through 30 November 2026. Set Opportunity Status to Open and add an Opportunity Name filter containing `CRM Report Pilot` to isolate the exercise.

| Filter | Sample value | Excluded case | Common mistake |
| --- | --- | --- | --- |
| Show Me | All opportunities available to the intended user | Records outside the approved access model | Leaving a personal-only scope unintentionally |
| Close Date | 1 to 30 November 2026 | December opportunity | Using Created Date for a closing-period question |
| Opportunity Status | Open | Won opportunity | Treating all stages as current pipeline |
| Opportunity Name | Contains CRM Report Pilot | Unrelated business records | Reconciling a test total against the whole org |

The [summary-report exercise](https://trailhead.salesforce.com/content/learn/projects/create-reports-and-dashboards-for-sales-and-marketing-managers/create-a-simple-custom-report) demonstrates these types of standard filters. The fixed calendar range above replaces its relative period so the fixture can be repeated without changing as time passes.

Relative filters such as a current fiscal quarter are useful for an ongoing report, but they change the selected period. Record the intended fiscal calendar and date field in the report description. A chart that changes after a period boundary may be operating correctly rather than losing data.

Keep the sample filter separate from the production scope. Once validation is complete, replace the pilot-name condition with the actual approved business criteria and reconcile a representative production sample. Removing the test filter can reveal additional record types, currencies or ownership cases that the small fixture did not cover.

## Columns, grouping and totals

For this report, include Opportunity Name, Account Name, Opportunity Owner, Stage, Close Date and Amount. Keep the columns that let a reader explain why a row belongs and what its value means. Extra fields can make an exception harder to inspect without improving the decision.

Group rows by Opportunity Owner and summarize Amount with Sum. The resulting sample should show Alex at $12,000, Sam at $8,000 and a $20,000 total. Salesforce's [summary-report instructions](https://trailhead.salesforce.com/content/learn/projects/create-reports-and-dashboards-for-sales-and-marketing-managers/create-a-simple-custom-report) describe owner grouping and the sum setting.

Count records and sum amounts as separate checks. Two rows totaling $20,000 are different evidence from a total alone. A missing $8,000 opportunity and an incorrectly included $8,000 opportunity could leave the same aggregate while representing the wrong customers.

The example assumes one currency and one opportunity per displayed detail row. If the production report spans currencies or includes related-object detail, qualify the aggregation before using the total. Link back to the report-type design and currency rules rather than treating a sum as automatically comparable across every report.

## A useful report chart

Add a chart after the detail rows and totals reconcile. A horizontal or vertical bar chart can compare the two owner subtotals in the example. Label the measure as open opportunity amount for the selected close-date period, rather than a general Revenue label.

Salesforce supports a chart directly on a report as well as dashboard widgets. [Report charts and dashboards](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_reports_dashboards/lex_implementation_reports_dashboards_visualizing_data). A separate dashboard is unnecessary if the report and its chart already support the reader's decision.

Test the chart against the detail. Selecting a different measure, grouping or dashboard filter can change what it represents. The chart title, selected period and underlying records should agree before the report becomes part of a management review.

Use the [dashboard templates](https://www.martechdevs.com/tools/dashboard-templates) to outline the measures and layout before creating a larger dashboard. Keep each component tied to an accepted source report.

## Folder sharing and ordinary-user checks

Save the report in the folder intended for its audience. Salesforce's [folder-sharing guide](https://help.salesforce.com/s/articleView?id=analytics.rd_folders_share_enhanced.htm&language=en_US&type=5) describes sharing a Lightning report or dashboard folder with users, groups, roles or territories and selecting the access level.

1. Open the relevant folder list from Reports, Dashboards or Analytics.
2. Find the folder and select Share from its action menu.
3. Choose the intended audience and appropriate folder access.
4. Apply the sharing change.
5. Ask an ordinary intended user to open and run the report.

Check both access to the report and the data it displays. The reader should be able to explain the included records under the approved security model. A working administrator view should not be the only acceptance evidence for a sales representative's report.

Assign a continuing report owner. That person maintains the description, filters, folder audience and dependencies. A shared folder makes a report discoverable; it does not by itself establish who should approve a changed metric definition.

## Dashboard visibility and running context

A dashboard adds another context to the source report. Salesforce's [dynamic-dashboard guide](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_reports_dashboards/lex_implementation_reports_dashboards_visualizing_data) explains that a dynamic dashboard can show data according to the viewing user's access. Its configuration uses the dashboard viewer as the viewing context.

Select the intended behavior explicitly and qualify feature availability in the org. Test a representative and a manager separately. Different totals can be correct when their permitted record populations differ, but the reason should be visible in the dashboard's purpose and configuration.

Also share the required dashboard and report folders with the intended audience. Keep the source report usable so a manager can inspect the records behind a chart instead of treating the dashboard as an unexplained final number.

## Subscriptions and exported results

A report subscription sends refreshed results on a schedule. Salesforce's [subscription guide](https://help.salesforce.com/s/articleView?id=sf.reports_subscribe_lex.htm&language=en_US&type=5) includes a Run Report As setting. Recipients see the selected running user's report data, which can differ from what they normally see when using Salesforce themselves.

Review recipients and running context before enabling distribution. A correctly shared folder does not settle every question about the data included in an emailed report. Record the business purpose of the distribution and the owner responsible for maintaining it.

Attachments also have limits. Salesforce's [attachment guide](https://help.salesforce.com/s/articleView?id=sf.reports_subscribe_attachment.htm&language=en_US&type=5) lists a maximum of 15,000 rows, thirty columns and a 3-MB file size, with extra data clipped or not sent. A received attachment should therefore not automatically be treated as a complete large-data export.

Use an appropriate extraction route when the job is data movement rather than human reporting. The [Data Loader guide](https://www.martechdevs.com/blog/salesforce-data-loader) and [Workbench replacement workflow](https://www.martechdevs.com/blog/salesforce-workbench) cover record extraction and result reconciliation. Preserve the report's filter and identity definitions when comparing those outputs.

## Report troubleshooting

| Symptom | First evidence | Repair area | Recheck |
| --- | --- | --- | --- |
| No rows in preview | Date, scope and sample records | Filter or access | Run the report with known included records |
| Correct count but wrong total | Amount values and aggregation | Measure or currency | Owner subtotals and detail rows |
| Missing expected opportunity | Type, status, date and visibility | Population definition | One included and one excluded case |
| Manager and representative differ | Running context and record access | Intended audience model | Each ordinary user separately |
| Dashboard differs from report | Dashboard filters and source selection | Presentation context | Same source report and period |
| Email attachment is incomplete | Attachment limits and row count | Distribution method | Full intended result through a suitable route |

Do not repair a filter problem by changing the source record to make the chart look right. Confirm the business truth first. If the record itself is incorrect, route that correction to its owner and preserve the reason for the change.

## Reporting validation workflow

![A business question and known sample define the report. Population repairs repeat configuration; sharing or viewing-context repairs repeat report execution before maintained chart or subscription use.](https://www.martechdevs.com/assets/blog/salesforce-reports.svg)

Diagram connections:

- Business question and known sample to Report type fields and filters. 
- Report type fields and filters to Saved report execution. 
- Saved report execution to Expected records and totals. 
- Expected records and totals to Population or measure repair: No. 
- Population or measure repair to Report type fields and filters. 
- Expected records and totals to Folder and viewing-context checks: Yes. 
- Folder and viewing-context checks to Accepted audience and visibility. 
- Accepted audience and visibility to Sharing or running-context repair: No. 
- Sharing or running-context repair to Saved report execution. 
- Accepted audience and visibility to Chart subscription and maintained owner: Yes

The access repair returns to report execution because changing the viewing context can change the data. The report is ready for regular use when both the numerical result and the intended audience have passed their checks.

## Salesforce report checklist

- [ ] Define the business question, record unit and intended audience.
- [ ] Confirm report-building and running permissions.
- [ ] Select the report type for the required records and fields.
- [ ] Set scope, date field, period and status deliberately.
- [ ] Run the report instead of relying only on its preview.
- [ ] Reconcile included records, excluded cases and subtotals.
- [ ] Add charts only after the source result is accepted.
- [ ] Test folder access and viewing context with ordinary users.
- [ ] Review subscription recipients, running user and attachment limits.
- [ ] Assign an owner for definitions, filters and future changes.

The [CRM data hygiene audit skill](https://www.martechdevs.com/skills/crm-data-hygiene-audit) helps establish the known customer and opportunity sample. Keep it with the report definition so later filter or process changes can be checked against the same expectations.

## Frequently asked questions

### Does the Salesforce Report Builder preview contain every matching record?

The Report Builder preview does not contain every matching record. Salesforce describes it as a limited sample for editing and instructs users to run the report for the full result. Validate the executed report against known included and excluded cases, then reconcile detail counts and totals before using the preview's appearance as evidence that the report is complete.

### Should Created Date and Close Date be interchangeable in an opportunity report?

Created Date and Close Date should not be treated as interchangeable. Created Date supports a question about opportunities entering the system, while Close Date supports a question about the expected or recorded closing period. Choose the date field from the business question and state it in the report description so readers can interpret the population and period correctly.

### Can a correct grand total conceal incorrect Salesforce report rows?

A correct grand total can conceal incorrect rows when missing and wrongly included amounts offset each other. Check record identities and exclusion cases as well as the aggregate. Reconcile group subtotals and the intended reporting grain, particularly after adding relationships or changing filters, so a plausible total does not hide the wrong customer or opportunity population.

### Do report-subscription recipients always see their own Salesforce data view?

Report-subscription recipients do not always see their own normal Salesforce data view. The subscription can run as the subscribing user or another configured person, and recipients receive that running user's report data. Review the running context and audience together before enabling distribution, especially when a manager and individual sellers normally have different record visibility.

### Is a Salesforce subscription attachment a guaranteed complete bulk export?

A Salesforce subscription attachment is not a guaranteed complete bulk export. Salesforce documents limits for rows, columns and file size, with additional data clipped or not sent. Use the attachment for the defined reporting purpose and verify its scope. For larger data movement, select an extraction method that supports complete-result handling and reconcile it separately.

## Sources

1. [Salesforce Lightning Report Builder](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_reports_dashboards/lex_implementation_reports_dashboards_using_report_builder)

2. [Salesforce opportunity summary-report example](https://trailhead.salesforce.com/content/learn/projects/create-reports-and-dashboards-for-sales-and-marketing-managers/create-a-simple-custom-report)

3. [Salesforce report creation permissions](https://help.salesforce.com/s/articleView?id=analytics.reports_custom.htm&language=en_US&type=5)

4. [Salesforce Lightning folder sharing](https://help.salesforce.com/s/articleView?id=analytics.rd_folders_share_enhanced.htm&language=en_US&type=5)

5. [Salesforce report charts and dynamic dashboards](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_reports_dashboards/lex_implementation_reports_dashboards_visualizing_data)

6. [Salesforce report subscriptions and running users](https://help.salesforce.com/s/articleView?id=sf.reports_subscribe_lex.htm&language=en_US&type=5)

7. [Salesforce report subscription attachment limits](https://help.salesforce.com/s/articleView?id=sf.reports_subscribe_attachment.htm&language=en_US&type=5)
