using vscode to fix reports that break from configuration changes
Summary
Changes to Salesforce configurations like picklist updates can break many reports at once, creating deployment headaches. Using VS Code along with Salesforce CLI commands like force:source:tracking:reset allows selective retrieval and deployment of only modified reports rather than all reports. This technique helps avoid bulk redeployment issues and enables easier error management using .forceignore. Combining this approach with Salesforce DevOps Center streamlines moving fixed reports from sandbox to production with precise control.
Takeaways
- Use package generator extension in VS Code to retrieve all Salesforce reports locally.
- Run sfdx force:source:tracking:reset before find/replace to track only modified reports.
- Apply find/replace in VS Code to update configuration values in reports efficiently.
- Use .forceignore to exclude reports with errors during deployment retries.
- Leverage DevOps Center to manage and deploy updated reports from sandbox to production.
changes to configuration, like updating picklist values, can easily mess up salesforce reports, which is a perennial problem for yours truly. i think sometime in the middle ages i dealt with this using eclipse but only vague memories remain. working today on using vscode to deal with this…first I needed to get all reports locally. this post on dev forum suggested a nifty package generator extension I used that extension to generate the package. check the “report” metadata type and it crunched through all 6k(!) reports we have and created a package.xml file then i could easily retrieve all reports by right clicking on the package.xml file and selecting “retreive source from org using manifest” in vscode! i then used find/replace in folder to update the old picklist value to the new one! but if I then use force:source:push it deploys all reports , not just the modified ones.