Loading

Resolve common errors for Dashboard Components

Publish Date: May 5, 2026
Description

A Salesforce admin receives a support ticket from a sales manager whose dashboard components are showing errors after a recent profile change. This article covers the most common dashboard component errors and how to resolve each one.

Resolution


"This report cannot be used as the source for this component. If it is a summary or matrix report, add one or more groupings in the report. If it is a tabular report with a row limit, specify the Dashboard settings in the report."

  • For a Summary or Matrix format, you need to add one or more groupings in the report.
  • If the source report of the dashboard's component is in Summary format, make sure that the Running User of the dashboard has at least "read only" access to the field that is used to summarize or group the report.
  • If the report is in a Tabular format, make sure that you click the Add dropdown menu next to "Filters," click on Row Limit, then enter a row limit. After adding the row limit, a "Dashboard Settings" button will appear next to the "Run Report" button. Click the button, choose the Names and Values to use in dashboard tables and charts, and save. The Running User of the dashboard has at least "Read Only" access to the fields specified in the Dashboard Settings of the source report.

 

"__MISSING LABEL__ PropertyFile - val SubscribingFromInactiveException_desc not found in section Exception."

This error occurs when saving a dashboard.

Workaround: Clone the dashboard and use the newly created one instead of the original.

 

"The running user for this dashboard does not have permission to run reports. Your system administrator should select a different running user for this dashboard."

This error means that the Running User set for the dashboard does not have the Running User Permission in the profile. The Running User is the Salesforce user whose permissions and data access determine what records appear in the dashboard, regardless of who is viewing it.

Have a system administrator follow these steps:

  1. Go to the Dashboard with the error message and click Edit.
  2. Check who the Running User is in the Dashboard Properties.
  3. Search this User to find out which profile they have.
  4. Click the profile name and go to the "General User Permissions" section.
  5. Look for the "Run Reports" permission.

 

"The Running User for this Dashboard is inactive. Your system administrator should select an active user for this Dashboard."

You have an Inactive User listed as the "Running User" for the dashboard you are trying to view. You'll need to update this User to view the dashboard.

 

"One or more of the fields selected in the component is no longer available in the report. Use the dashboard component editor to select one of the available fields."

This error occurs when the Running User of the dashboard does not have access to the field that is set in the dashboard. One example is that the Custom Summary Formula is referencing two fields (for example,  Amount:Sum + Custom_Field_c:Sum). If a User doesn't have access to either field, you'll get the error.

Follow these steps:

  1. Review the fields in the report that are used in the Dashboard, such as the fields referenced in the Custom Summary Fields.
  2. In Classic, go to Setup | Customize (Classic) or Object Manager (Lightning) | Object (where the field in the report is located) | Fields
  3. Click the field that you used in the Dashboard, then click Field-Level Security.
  4. Select Visible for the relevant profile.
  5. Click Save.

 

"Warning: the results below may be incomplete because the underlying report produced too many summary rows and the sort order of the component is different from the sort order in the underlying report. Try adding filters to the report to reduce the number of rows returned."

Open the source report and try to reduce the grouping's row results. For example, for Date fields, change the grouping from Daily to Monthly or remove a grouping level.

 

"Too Many Dashboard Components. A single dashboard may contain at most 20 components."

This error can happen even if you can see fewer than 20 components on your dashboard.

Examples:

  • When you change the Dashboard Layout Style from 3 to 2, as one column of components will be hidden but still counted
  • When cloning a dashboard from 3 columns Layout to 2 columns
  • When the original dashboard components have already reached the 20 components limit  
 

To fix the issue: Edit the Dashboard Properties by changing the Dashboard Layout Style from 2 to 3. Remove components from the extra column and reedit the layout style from 3 to 2.

 

"Can't save dashboard with incomplete components. Each component must have a type and a data source. Please complete components before saving."

You either need to add the Component Type or a Source Report to a component.

 

"The source report isn't available; it's been deleted or isn't in a folder accessible to the Dashboard running user."

This error happens with Dynamic Dashboards if the source report is in a folder not shared with the Running User. To resolve this, share the folder where the source report is present to the affected User.
 

Related Video:  Manage Report and Dashboard Folders (Lightning Experience) | Salesforce
 

"Dashboard is visible. The moment you click on the component it throws an error 'Data Not Available."

This error can happen with a "static dashboard." This means the dashboard folder is shared with the User, but the source report is not.

 

"Please have your administrator enable at least one dashboard for you to view" when customizing the Home Page."

Received by Users who don't have access to any dashboard in the organization. Ensure that the affected user is given access to the Dashboard folder.

 

"Unable to run Source Report because it's definition is invalid"

This error indicates that the filter criteria has an invalid reference. This typically occurs when a field used as a filter within the report is hidden from the Running User of the Dashboard via Field Level Security. A reference within the Filter Logic (For example, 1 AND (2 OR 3) AND 4) will cause this to occur as the row for this hidden field will be unpopulated.

There are a few options available:

  • Remove the Filter Logic
  • Modify the Profile of the Running User to allow access to the hidden field
  • Change the Field-Level Security for the Running User's profile to allow them to see all filters and grouped fields within the report

 

"Can’t load component because the source report didn’t finish running."

This error message indicates an issue with the dashboard component's performance. See the article on improving dashboard performance for tips on resolving the error.
 

"Sorry to interrupt: This page has an error. You might just need to refresh it. [PromiseRejection: [object Object]]"

At least one underlying source report cannot be run because it was saved in an incorrect state. Locate an affected component and either rebuild its source report or make a small change to it in the Classic Builder and save.
 

"Unsupported report type"

This error occurs when a measure is sorted on a Dashboard component that has more than 11,000 grouped rows. This error can be avoided by changing or removing a grouped field in the component or sorting on a different field.

 

"The component can't be displayed because the field(s) you chose for the filter are unavailable."

This error appears because the malfunctioning component's report does not contain an equivalent field with the rest of the components.

To resolve the issue, complete either of the following actions:

  • Edit the source report of the malfunctioning dashboard component to include the missing field (the field used in the dashboard filter)
OR
  • Remove the component or the filter from the dashboard.
 

"Invalid number of layout components. The number of components in the layout must equal the number of components in the metadata body."

Possible workaround is to delete and recreate the component. 
Trailblazer Community post .
 

"Cannot read properties of undefined (reading 'getAssetsPath')"

This error can occur when the user who created the dashboard is inactive. Contact the System Administrator to replace the user with the active user. 

Knowledge Article Number

000386112

 
Loading
Salesforce Help | Article