Skip to main content
All CollectionsTroubleshootingSalesforce validation errorsSalesforce validation errors
Resolving validation errors - "In field: report - no Report named <xxx> found" on Dashboard metadata type
Resolving validation errors - "In field: report - no Report named <xxx> found" on Dashboard metadata type

Guidance on how to resolve this Salesforce validation error happening on 'Dashboard' metadata type

Mateusz Kochanowicz avatar
Written by Mateusz Kochanowicz
Updated over a week ago

Explanation of the error:

This Salesforce validation error that Gearset is surfacing is likely to occur on the Dashboard metadata type.
​
​ In field: report - no Report named <xxx> found - where <xxx> refers to a specific report name.

We have seen this error happening when users deploy a new Dashboard that references a new Report, where both Dashboard and Report don't exist in the target environment.

Resolution:

If you're making your deployment via 'Compare and deploy' or a CI job (including a CI job in Pipelines), make sure to add Report type to your metadata filter.

This should resolve the validation error as a correct report type is required for a successful validation.


Troubleshooting steps when the error is surfaced on a Delta CI job:

If your CI job is configured as Delta CI, please check if your Delta CI metadata filter includes the Report type metadata type.


Next step: if your Delta CI comparison didn't include the 'Report type' metadata type

To verify that it is indeed the missing Report type metadata type causing the issue in your Delta CI job, you can run a manual comparison through a 'Compare and deploy' between your source environment (e.g. a feature branch if you're promoting changes via Pipeline) and the target environment (e.g. Salesforce org).
​
You should add all the items that were in your original deployment package (or in a Pull Request if you're promoting changes via Pipeline) + the Record type metadata type, and validate the package against the target org.

If the validation is successful, consider deploying your changes through a 'Compare and deploy'.
​
If you're unable to promote changes via 'Compare and deploy' because, for example, it's required to push the change via open PR in the Pipeline, feel free to contact us via in-app chat for further guidance.

Disclaimer: This error is returned by Salesforce directly, rather than Gearset. Even so, we offer guidance based on our combined experience with the Metadata API. Where possible, we try to help guide you to fix or avoid this error. In the case that this isn't possible, we may need to direct you to Salesforce support for further clarification.

Did this answer your question?