martinsdahl

@mikemccaffrey@drupal.community Its tricky. The dependency system solves alot of complex problems. But induces behaviour like this to prevent missing dependencies in the current state. Did you not get a list of dependent views when you were asked to confirm the deletion?

@mikemccaffrey@drupal.community I totally understand, and we have many times also experienced the same unwanted deletion of views. One could pitch a "soft dependency" concept to core. I believe that many modules could implement a kind of "remove soft dependencies of the following dependants", which for views would be to remove these fields from the SELECT statement. However, If the view had relationships or filters dependent on certain fields, the case is no longer clear and manual resolve is required.