Under Community Review

That's a good use case as a candidate for Where Used relationships. For Sites 9.5, we explicitly looked at Where Used as the check for the things that would prevent a user from deleting some item in the system. We actually removed some items from the lists that didn't actually prevent deleting the item in use.

A possible improvement to deletion would be a sort of "deletion wizard" or more powerful Where Used that let a user go through a process to delete an item, respecting user authorization settings while confirming steps along the way.

To help this idea along we could use votes as well as more use cases and feedback. How often does it come up that you can't delete a folder or some other item? Would additional information help?

Improve "item in use" error.

If you create a folder in a parent publication, but someone creates an item in that folder in a child publication, you cannot then delete the parent publication - the GUI gives the error "The item is in use".

The problem is that a Where Used wont show the fact that the folder has items within it. A user has to check the folder at each child publication - in larger blueprints this could be annoying!

Why can't the error message at least contain the context TCM Id of the folder from the child publication that is preventing deletion of the parent?