Cascade add is a huge help when tweaking data designer designs, as the early beta didn’t have this. The more complex the system the more obnoxious it was to add in a new field.
Can we get a similar functionality on delete? While it is true if you find out you have a field you don’t need you can simply not use it, but that isn’t great best practice, and for larger complex data sets having to go through and delete every instance of the field in top down order can be tedious, especially if your goal is to remove multiple fields, and perhaps even an entire object or merge.
There could be additional safeguards as well - for example if the set has been published, there could be a warning about causing instability with existing reports or dependencies if the action is completed, whereas if you’re still in preparation you would get a similar notification to the current cascade add feature.
