Common Errors

This report cannot be used as the source for this component.

• For a Summary or Matrix report: add one or more groupings in the report.
• Ensure the Running User has at least Read Only access to any field used to group or summarize the report.
• For a Tabular report: click Add (next to Filters) > Row Limit, enter a value. A Dashboard Settings button will appear — click it, choose the Names and Values for tables and charts, then save. Confirm the Running User has Read Only access to all fields specified in Dashboard Settings.

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...

• The Running User's profile is missing the Run Reports permission. 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:
  1. Open the dashboard and click Edit.
  2. Check the Running User in Dashboard Properties.
  3. Find that user's profile.
  4. Under General User Permissions, locate and enable Run Reports.

The Running User is inactive. 

• The Running User is inactive. Update the Running User to an active user to restore dashboard access.

One or more of the fields selected in the component is no longer available in the report...

• The Running User lacks Field-Level Security (FLS) access to a field used in the dashboard — including fields referenced in Custom Summary Formulas.
  1. For example: A Custom Summary Formula is referencing two fields ( Amount:Sum + Custom_Field_c:Sum). If the Running User doesn't have access to either field, you'll get the error. 

• To resolve the error follow these steps: 
  1. Identify the field(s) used in the dashboard component or summary formula.
  2. Go to Setup > Object Manager (Lightning) or Customize (Classic) > select the object > Fields.
  3. Click the field > Field-Level Security.
  4. Set Visible for the Running User's profile > 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. 

• Open the source report and reduce the number of grouped rows. For date fields, change the grouping granularity from Daily to Monthly, or remove a grouping level entirely.

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

• This can occur even when fewer than 20 components are visible — hidden components in collapsed columns still count toward the limit.

Common causes:

• Switching Dashboard Layout Style from 3 columns to 2 (components in the hidden column are still counted)
• Cloning a 3-column dashboard into a 2-column layout
• The original dashboard already at the 20-component limit

Fix:

1. Edit Dashboard Properties and change the Layout Style back to 3 columns.
2. Remove components from the extra column.
3. Re-edit the Layout Style back to 2 columns.

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

• Each component requires both a Component Type and a Source Report. Add the missing element to all incomplete components before saving.

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

• Common with Dynamic Dashboards. The source report folder is not shared with the Running User. Share the report folder with the affected user to resolve.
• Related Video: Manage Report and Dashboard Folders (Lightning Experience) | Salesforce

"Data Not Available"  error when clicking a dashboard component

• This is a "static dashboard" issue — the dashboard folder is shared with the user, but the source report folder is not. Share the source report folder with the affected user.

"Please have your administrator enable at least one dashboard for you to view" (Home Page customization)

• The user doesn't have access to any dashboard in the org. Grant the user access to at least one dashboard folder.

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

• A filter in the source report references a field hidden from the Running User via Field-Level Security. This is often triggered by Filter Logic (e.g., 1 AND (2 OR 3) AND 4) where one row is unpopulated due to a hidden field.

Options:

• Remove the Filter Logic
• Update the Running User's profile to grant access to the hidden field
• Adjust Field-Level Security so the Running User can see all filtered and grouped fields

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]]

1. Open the source report in Report Builder.
2. Change the sort field from a measure or Custom Summary Formula to a standard grouping field (e.g., a date, name, or picklist field).
3. Alternatively, reduce the number of grouped rows by adding filters or changing date grouping granularity (e.g., Daily → Monthly).
4. Save the report and refresh the dashboard component.

Note: If the measure-based sort is required for standalone report use, create a copy of the report specifically for the dashboard without the measure sort.

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

• Edit the source report to include the missing filter field, OR
• Remove the component or the dashboard filter.

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

• A mismatch exists between the layout and the component metadata. Delete and recreate the affected component. See also: Trailblazer Community discussion.

Cannot read properties of undefined (reading 'getAssetsPath')

• The user who created the dashboard is inactive. Have a System Administrator reassign the dashboard to an active user.

Lightning Experience — Known Limitations

The following configurations are not supported for dashboard components in Lightning Experience and will produce errors or unexpected behavior:

• Source reports sorted by a measure or Custom Summary Formula column with >11,000 grouped rows ("Unsupported report type")
• Joined Reports as dashboard component sources
• Tabular reports without a Row Limit set
• More than 20 components per dashboard (including components in hidden columns)

FAQ

Q: Why does my dashboard show different data than the source report?
A: Dashboards run as a specific Running User, whose data visibility may differ from yours. Check the Running User in Dashboard Properties and confirm their profile has access to the relevant records and fields.

Q: A dashboard worked in Classic but errors in Lightning Experience. Why?
A: Some report configurations supported in Classic are not supported in Lightning Experience — particularly measure-based sorting on large datasets. Review the Lightning Experience Known Limitations section above.

Q: My dashboard component says "Data Not Available" but the report runs fine. What's wrong?
A: This is usually a folder-sharing issue. The dashboard folder may be accessible to the user, but the source report folder is not. Share the source report folder with the affected user.

Q: What does the Running User setting control?
A: The Running User determines whose permissions and data access are used to populate the dashboard — regardless of who is viewing it. If the Running User lacks access to certain records or fields, those will not appear for any viewer.