Salesforce has redesigned and relocated the Metadata Coverage Report for Summer ’25. The legacy report will be removed in this release.
What changed
Salesforce has introduced a redesigned Metadata Coverage Report in the Summer ’25 release. This report lists which metadata types are supported by which deployment and retrieval tools (Metadata API, Source Tracking, Unlocked Packages, Change Sets, etc.). The older report will be deprecated and removed in Summer ’25, so admins and release engineers should update any bookmarks and automation that reference the legacy location.
Why this matters
Not all metadata types behave the same across tools. If a metadata type isn’t supported by the tool you’re using, deployments can fail or require manual steps. The new coverage report is the authoritative place to verify tool support before planning deployments or packaging metadata.
Where to find it
Refer to the official Summer ’25 release notes for the new report location and details: Salesforce Release Notes — Metadata Coverage Report.
Practical tips for admins & developers
- Update internal runbooks, CI configs, and bookmarks to point to the new report location.
- Before deploying, check the metadata type in the new report to confirm supported tools and any caveats.
- For types not supported by your primary tool, prepare an alternate plan (e.g., Metadata API package.xml retrieval, manual deployment, or using a supported packaging format).
- Subscribe to release notes or authoritative channels to catch any future metadata support changes early.
References & further reading
Salesforce Release Notes: New Metadata Coverage Report (Summer ’25)
Why this matters for Salesforce teams:
For admins, developers, and release engineers, verifying metadata-tool compatibility is a small step that prevents large deployment headaches. The redesigned report helps you plan packaging and CI/CD strategies more confidently — saving time and reducing failed deployments.