Reports and Dashboards Limits and Allocations

Salesforce Reports and Dashboards Allocations

These allocations apply to supported editions.

¹ These allocations apply to the report builder. If you’re using the report wizard, the allocation is 10.

² Up to 200 total.

³ Off-peak hours only, between 6 PM and 3 AM local time.

⁴ Limited to one preferred start time per day.

⁵ Limited to three preferred start times per day.

Report Limits, Limitations, Guidelines, and Considerations

These apply to reports in Lightning Experience and Salesforce Classic in all supported editions.

• The report builder preview shows a maximum of 20 rows for summary reports (grouped by rows) and matrix reports (grouped by columns), and 50 rows for tabular reports (no groupings).
• In Salesforce Classic, you can’t have more than 250 groups or 4,000 values in a chart. If you see an error message saying that your chart has too many groups or values to plot, adjust the report filters to reduce the number. In combination charts, all groups and values count against the total.
• In Lightning Experience, a report chart can have at most 2,000 groups. If a report has more than 2,000 groups, the Combine Small Groups into Others action applies only to the small groups within the 2,000 that are included in the report chart. Any additional small groups are ignored.
• If a report has more than 2,000 rows, the report chart doesn’t use the colors selected for picklist values in Object Manager. Instead, the chart uses the system-generated colors. To reduce the number of rows, apply filters or hide details.
• Reports display a maximum of 2,000 rows. To view more rows, export the report to Excel or use the printable view for tabular and summary reports. For joined reports, the printable view displays a maximum of 20,000 rows. The printable view is only available in Salesforce Classic.
  • Summary reports (grouped by rows) and matrix reports (grouped by columns) display the first 2,000 groupings when Show Details is disabled.
  • A matrix report with one summary formula can show a maximum of 400,000 summarized values, with up to 2000 rows and 200 columns. Each summary formula you add reduces the number of values, rows, and columns the report shows. For example, with two summary formulas, the maximum decreases to 200,000 values in 1,414 rows and 141 columns. Three summary formulas reduce the maximum results shown to 133,333 values in 1,154 rows and 115 columns.
  • Matrix reports that return more than 2,000 rows don’t show details. If you click Show Details, nothing happens. You can only view the report with details hidden. To see all details, use the Details Only export option.
  • Because a matrix report includes multiple groupings, the maximum of 2,000 values is typically reported in fewer than 2,000 groups.
  • Row counts and summaries can be inaccurate in a joined report with more than 2,000 rows, where one of the blocks takes up most of the rows.
• Up to 5 metrics display in the Lightning Experience report header. Metrics such as summarized fields appear in the order that they appear in the report, left to right. The grand total, when shown, always displays.
• When reports that have groupings are viewed in the Salesforce mobile app, they’re converted to tabular reports.
• The Salesforce mobile app supports a maximum of 25 report columns.
• By default, reports time out after 10 minutes.
• In a non-joined report, if you click a bar in a report chart, the report results are filtered according to the selected bar. In a joined report, clicking a bar doesn’t apply the filter.
• When searching for reports, if you filter on a long text area field, such as Description or Solution Details, only the first 1,000 characters of the field are searched.
• Some filters, such as date range, are constructed using multiple custom filters, each of which counts toward the total of 20.
• You can enter up to 1,333 characters for filter criteria, including commas used as OR operators.
• Field-to-field filtering isn’t available on currency fields for orgs that have multiple currencies enabled.
• The first 999 characters in a standard rich text area or a long text area are displayed in a report. For custom fields, only the first 254 characters are displayed.
• Summary fields on tabular, summary, and matrix reports can display up to 21 digits.
• You can’t filter reports by custom long text area fields.
• Filter logic doesn’t support locked filters. If you apply filter logic to a locked filter, the lock is removed.
• Forecast reports include only opportunities that are set to close within the forecast period.
• The maximum value allowed for report metrics is 999999999999999. The minimum value allowed is -99999999999999.
• The State/Province picklist filter converts the selected state or province to a two-digit code (example: MO for Missouri). If a state or province in another country covered by the report has the same code, for example, MO for Morales, Mexico, filtering on one of the states or provinces can return data for the other.
• HTML code isn’t supported in report charts.
• An object’s external organization-wide default must be set to private for an external user to view the object in a report. If an object's external organization-wide default can’t be set to private then an external user can’t view the object in a report.

Dashboard Limits, Limitations, Guidelines, and Considerations

These apply to dashboards in Lightning Experience and Salesforce Classic in all supported editions.

In Salesforce Classic, widgets are called components.

• A dashboard filter can have up to 50 values.
• Each dashboard can have up to 25 widgets, including a maximum of 20 charts and tables, 3 images, and 25 rich text widgets.
• A dashboard widget can calculate up to 1,000 groupings. Aggregated totals only reflect the values in the first 1,000 groupings. This limit applies to dashboard component calculations. In Salesforce Classic, report charts are limited to 250 groups.
• Sorting a dashboard component by a measure, such as Record Count, can cause an Unsupported Report Type error when the source report includes many records or unique groupings. To resolve the error, filter the report to reduce the number of records, remove groupings, or change the sort order.
• Currency symbols appear to the left of currency values in dashboard widgets.
• Filtering is restricted in some dashboards that contain multiple widgets based on different report types.
  • If a dashboard has a widget based on Cases or Leads and another widget based on a different report type, you can’t filter the dashboard on the Case Owner or Lead Owner field. In addition, filtering on other Owner fields doesn’t display Case Owner or Lead Owner as equivalent fields.
  • If a dashboard has a widget based on the Tasks and Events, Activities with Accounts, or Activities with Contacts report type and another widget based on a different report type, you can’t filter the dashboard on the Assigned field.
• A dashboard table or chart can display up to 20 images.
• Wait at least 1 minute between dashboard refreshes.
• Downloaded and shared images of dashboard widget tables have a maximum height of 3,000 pixels or approximately 100 rows. Rows beyond the limit are clipped. To avoid clipping, filter the chart to fewer than 100 rows.
• Each Financial Services Cloud org includes 10 licenses for dynamic dashboards, which is in addition to the licenses that are provided in your Salesforce edition.
• Each Enablement license add-on includes one additional dynamic dashboard.
• You can’t follow individual dashboard widgets in Lightning Experience.
• You can’t follow individual widgets in a dynamic dashboard.
• You can change ownership of up to 50 dashboards at one time.
• When a dashboard is refreshed, the Last Run Date field of a source report is not updated if the report is used only in a Lightning table component. This is because the Lightning table loads report metadata instead of running the full report. To update the Last Run Date, include another dashboard widget such as a chart, gauge, or metric that uses the same report.
• The View Dashboard As feature isn’t supported on dashboards that include custom Lightning Web Components.
• When you select Use table settings from report, you can add up to three Lightning tables to a dashboard.

Report Export Limits and Considerations

When exporting report data, keep these limits and considerations in mind.

Custom Report Type Limits, Limitations, Guidelines, and Considerations

These apply to custom report types in supported editions.

• A custom report type can contain up to 60 object references. For example, if you select the maximum limit of four object relationships for a report type, you can select fields via lookup from an extra 56 objects.
• If a user runs a report from a custom report type and the report has columns from more than 20 different objects, an error occurs.
• You can add up to 1,000 fields to each custom report type. A counter at the top of the Page Layout step shows the current number of fields. If you have too many fields, you can’t save the layout.
• You can’t add these fields to custom report types:
  • Product schedule fields
  • History fields
  • The Age field on cases and opportunities
• Custom report types based on the Service Appointments object don’t support these fields.
  • Parent Record
  • Owner
• Object references can be used as the main four objects, as sources of fields via lookup, or as objects used to traverse relationships. Each referenced object counts toward the maximum limit even if no fields are chosen from it. For example, if you do a lookup from account to account owner’s role, but select no fields from account owner, all the referenced objects still count toward the limit of 60.
• Reports run from custom report types that include cases don’t display the Units dropdown list, which lets users view the time values of certain case fields by hours, minutes, or days.
• Report types associated with custom objects in the Deleted Custom Objects list count against the maximum number of custom report types you can create.
• Reports on feed activities don’t include information about system-generated posts, such as feed tracked changes.
• Custom report type names support up to 50 characters. If you enter a name that is longer than 50 characters, the name gets truncated.
• Custom report type descriptions support up to 255 characters. If you enter a name that is longer than 255 characters, the name gets truncated.
• When a lookup relationship is created for a standard or custom object as an Opportunity Product field, and then a custom report type is created with that primary object, Opportunity Product isn’t available as a secondary object for that custom report type.
• To report on gender-related data, make sure that the top-level object in the report is Contact, Lead, or Person Account. For example, a report with Campaign as the top-level object doesn’t have the GenderIdentity field available.

Joined Report Limits, Limitations, and Considerations

These apply to joined reports in all supported editions.

• Joined reports require that the new user interface theme is enabled. Users without the new theme are unable to create, edit, or run joined reports.
• In a joined report, each block can have up to 100 columns. A joined report can have up to 5 blocks.
• When you add a block to a joined report and the block has multiple entities in common with the report, only the first entity, in alphabetical order, is shown. Only the fields from the first entity are shown in the common fields area.
• You can add up to 10 custom summary formulas to each block in a joined report. A joined report can have a total of 50 custom summary formulas.
• Each joined report can have up to 10 cross-block custom summary formulas.
• You can add the chart from a joined report as a dashboard widget, but you can’t add the full report. Filtering isn’t supported for widgets with a joined report chart.
• Internet Explorer 6 isn’t supported for joined reports.

Reporting Snapshot Limits

These limits apply to all supported editions.

• The maximum number of rows that you can insert into a custom object is 2,000.
• The maximum number of runs that you can store is 200.
• The maximum number of source report columns that you can map to target fields is 100.

Cross Filter Limits and Considerations

Consider these limits when working with cross filters.

• Each report can have up to 3 cross filters.
• Each cross filter can have up to 5 subfilters.
• Filter logic applies only to field filters, not cross filters.

Embedded Report Charts Limits, Limitations, and Considerations

Keep these considerations and limits in mind when embedding report charts.

• You can have two report charts per page.
• You can only add report charts from the enhanced page layout editor. The mini console and the original page layout editor aren’t supported.
• In Lightning Experience, embedded report charts display the source report table’s groupings, not the report chart’s. In Salesforce Classic, embedded report charts display the source report chart’s grouping, not the report table’s groupings.
• On detail pages, users can refresh up to 100 report charts every 60 minutes.
• Your org can refresh up to 3,000 report charts every 60 minutes.

Bucket and Bucket Field Limits, Limitations, and Considerations

These limits and considerations apply to bucketed report fields in all supported editions.

• Each report can include up to 5 bucket fields.
• Each bucket field can contain up to 20 buckets.
• Each bucket can contain up to 20 values.
• Bucket fields are available for use only in the report where they’re generated. To use a bucket in multiple reports, create the field for each report, or create a separate formula field for the object that’s dependent on the bucket.
  

  Note These limits don’t apply to the use of Other as permitted within the bucket field’s setup.
• Buckets and bucket fields aren’t available for reports that include external objects.
• If a bucket field’s source column has a custom index, and you filter by the bucket field, then the performance gains from the custom index are lost.
• You can add a report with a bucket field to a dashboard, but you can’t filter on the field that’s bucketed.

Historical Trend Report Limits, Limitations, Considerations, and Guidelines

Keep these limitations and guidelines in mind when working with historical trend reports.

• Salesforce retains historical data for the previous 3 months, plus the current month. If you enable Historical Trending in Pipeline Inspection, up to 12 months of Opportunity history is stored.
• Up to 5 million rows of historical trending data can be stored for each object. Historical data capture stops when the limit is exceeded. The admin is alerted by email when any object reaches 70 percent of the limit, and again if the limit is exceeded.
• Each historical trend report can contain up to 100 fields. In Opportunities reports, the fields include standard preselected fields, which can’t be disabled.
• For historical trend reports in Lightning Experience, you must set the snapshot date as the primary row grouping.
• Formula fields aren’t supported.
• Row limit filters aren’t supported.
• The summary report format isn’t supported.
• You can specify up to 5 historical snapshot dates in each historical trend report.
• You can use up to 4 historical filters on each historical trend report.
• These field types are supported: Number, Currency, Date, Picklist, Lookup.
• Dynamic exchange rates aren’t supported. When you run a historical trend report, it uses a static exchange rate, which could be outdated.
• Internet Explorer 6 isn’t supported.
• You can’t subscribe to historical trend reports.
• The Report Wizard isn’t supported. Historical trend reports can only be created with the Report Builder.
• Historical trend reporting with charts is supported in Lightning Experience, but tabular views of historical trend reports aren’t available.
• Historical trending reports can’t be exported.
• When you enable historical trending, data collection starts from when the record was last modified.

Important If a picklist field is already being used in a historical trending data filter, consider the impact before changing any of its values. You could make that field less useful for historical reporting in the future.

Considerations When Running Reports and Dashboards in Different Locales

Keep these considerations in mind when viewing reports and dashboards across different locations.

When the running user and the viewing user are in different locales, there are some differences in how reports and dashboards are presented. For examples, see Configure Dashboard Data Visibility in Lightning Experience.

• With reports, the locale of the viewing user is respected. The report contents are always presented relative to the viewing user’s locale.
• With static (not dynamic) dashboards, all date/time fields are presented in the locale of the running user, not the viewing user.
• With dynamic dashboards, the running user can specify how the viewing user sees the dashboard: as the running user, the dashboard viewer, or another person.

External Object Report Limits, Limitations, and Considerations

Consider these limitations when reporting on external objects.

• If your report includes an external object, the results probably don’t reflect the full dataset. External objects behave similarly to custom objects, except that they map to data that’s stored outside your Salesforce org.
• A report that includes an external object fetches up to 20,000 records for the primary object and can encounter callout limits while fetching external object data. If the report results in few or no rows, try customizing the report to obtain more relevant external object rows.
• If a report contains external objects, it doesn’t show converted currencies.
• Field-to-field filters are unavailable in report types that reference an external object.
• The following features are not supported in reports containing external objects.
  • Converted currency fields
  • Cross filters
  • Buckets and bucket fields
  • Historical trend reporting
  • Row-level formulas
• If a report includes external objects and uses the OR operator in the filter logic, an error message appears when you save and run the report.

Lightning Experience Report and Dashboard Subscriptions Considerations, Limitations, and Limits

These limits and considerations apply to report and dashboard subscriptions.

Lightning Experience on Apple® iPad® Safari®

Keep these limitations in mind when working with reports and dashboards on Apple iPad Safari.

When you build or edit reports with Lightning Experience on Apple iPad Safari, you can’t drag fields and columns in the Fields and Overview panes. As a workaround, add columns using the Add column lookup. To reorder columns, remove them from the report and then add them back in the order you prefer.

When you build or edit dashboards with Lightning Experience on Apple iPad Safari, you can’t drag widgets to reposition or resize them. We recommend that you use Lightning Experience on a desktop to reposition or resize dashboard widgets.

Reports and Dashboards API Limits and Limitations

These limits and limitations apply to both the Reports and Dashboards REST API and the Reports and Dashboards API via Apex.

• Cross filters, standard report filters, and filtering by row limit are unavailable when filtering data.
• Historical trending reports are only supported for matrix reports.
• Subscriptions aren’t supported for historical tracking reports.
• The API can process only reports that contain up to 100 fields selected as columns.
• A list of up to 200 recently viewed reports can be returned.
• Your org can request up to 500 synchronous report runs per hour.
• The API supports up to 20 synchronous report run requests at a time.
• A list of up to 2,000 instances of a report that was run asynchronously can be returned.
• The API supports up to 200 requests at a time to get results of asynchronous report runs.
• Your organization can request up to 1,200 asynchronous requests per hour.
• Asynchronous report run results are available within a 24-hour rolling period.
• The API returns up to the first 2,000 report rows. You can narrow the results using filters.
• You can add up to 20 custom field filters when you run a report.
• If a report is run on a standard or custom object as an automated process user from an Apex test class, only the required custom fields are returned. Non-required custom fields aren’t shown in the results.
• • Your org can request up to 200 dashboard refreshes per hour.
  • Your org can request results for up to 5,000 dashboards per hour.