One use case we are in desperate need for this function is standard hardware. As there is a list of standard diameter and pitch combinations, we don't want two nodes for imperial and metric. Plus 2 nodes makes filtering less robust when they are in essence the same. More importantly it makes administration more difficult because now we must duplicate everything.to separate the nodes or build a huge list which is both metric and imperial. AND there can be a wrong combination of diameter and pitch during setup if they are merged together (attribute for pitch and attribute for diameter). Once everything exists it isn't a big deal but we aren't going to pre-populate a bunch of components that aren't used anywhere. And for custom lengths, again we need the correct combination of pitch and diameter. This is just one use case. The same use cases apply to almost all purchased hardware. In summary, it's about maximizing the lists for easy filtering and simplifying the choices for the users.
Hello @nsamardzija, any plans on this feature in classification?
It can easily reduce need for creation of two or more nodes just because we want ho have pre-defined attribute values wihch are depended on other. Today only way how to secure it is to have a new classification node where those are set as default with no other option.
With this cascading attribute values feature where list of attribute values is corrected based on selection of other selected attribute value will help to decrease number of nodes which are needed to maintain.
