As an MBA user,
- "Show Where Used" and "Remove/Delete" to check the same dependencies consistently
- This also implies that "Show Where Used" check all dependencies
- I can trust there are no dependencies when "Show Where Used" shows an empty result
The benefits are:
- It becomes much easier to safely remove things
- It becomes much easier to safely make major changes
- It reduces the risk of a non-functioning repository as MooD models may behave strangely when dependencies have been removed.
- "Show Where Used" show all dependencies
- If "Show Where Used" show an empty result, "Remove/Delete" cannot show a warning about dependencies. (And removing the warning from "Remove/Delete" is not an option).
Current (in 16.0.57.03), I run into many situations when I want to delete something from a repository, where I first use "Show Where Used" to make sure there are no dependencies, but when I afterwards try to delete it, I get a warning that it is being used. I have gone as far as inspect the SQL statements from MBA to figure out the dependencies. To say the least, this is a frustrating and time-consuming exercise. After I have done this for a while, it is clear to me that MBA uses two different implementations to find dependencies. So, this request for having one single and consistent implementation for finding dependencies. Also, the functionality to find dependencies when deleting seem to be more thorough than “Show Where Used”.
Here are a couple of "Show Where Used" issues that I have recently encountered:
- A model master is used as parent model for another model master.
- A model master is used in a menu panel.
Please sign in to leave a comment.