The Symptome
Your deployment fails with an error message like this:
ImportAsHolding failed with exception :The SavedQuery(...) component cannot be deleted because it is referenced by 1 other components. For a list of referenced components, use the RetrieveDependenciesForDeleteRequest.
The Cause
In your deployed solution, you removed a component. This could have been a view, a form, a column, etc. In your DEV environment it seemed straight-forward. You checked, that no other component in your solution is using the unwanted component and when there were no more dependencies, you removed the component from your solution or worse, you deleted the component from your DEV environment.
The issue is that the Power Platform Pipeline is not as smart about the order of operations. It wants to delete the component before it has been cleared of the dependencies in the target environment - so exactly the opposite of what you did on your DEV environment. And of course since the dependency is still present, it can't delete the component.
How to Fix: Remove the dependency by hand on the target environment
If you simply removed the component from your solution on DEV, then re-add it too your solution and follow the method below ("How to Avoid"). If not, you need to remove the dependency by hand on your managed target environment(s). Here's how you can do that.
Deactivate "Block unmanaged customizations" in your target environment (Power Platform Admin Center - Settings - Product - Features).
Open the "Default Solution" on the target environment and find the component you'd like to delete. Use the tree dots next to it to show the dependencies.
Then also uses the "Default Solution" to navigate to all the components that still have your unwanted component and remove the dependency by hand.
Do a sanity check again and see if the unwanted component has no more dependencies listed. Publish all customizations.
Now re-deploy the solution from your DEV environment.
If all went smoothly, activate "Block unmanaged customizations" again.
How to Avoid
Generally, be cautious with "delete from environment" on your DEV environment. It's better to execute such removals in two steps.
A) Deploy a version with the component still part of the solution, but all dependencies removed to it (by other components). Don't forget to publish all customizations before deploying. After deployment, confirm that the component has indeed no more dependencies on the target environment.
