ProfessorProfessorThat was my fear... makes it hard to differentiate common types of devices across a broad set of groups to make them change a common prop/threshold.
I'd thought it worked backwards from the device up until it found a setting. I know from other pieces that evaluations in some cases are alphabetical rather than by index/ID (Object Creation order). I may test with a group alphabetically sooner than "Clients/" to see if it changes the behavior.
NeophyteI haven't had to create any dummy resource folders (yet) to force a particular depth, but I figured this type of conflict came up in our environment then I would just come up with some naming standard that is obvious that is what the folder is for, like "LM_Force_Depth" or something like that.
The good news to me is that there's consistent rule for this one so we can fudge it if necessary with a minor workaround like this.
