I wanted to see whether other customers have run into the same limitation with column sets and dependent structures.
In our environment, we use dependency logic across structures/attributes so that when a user selects one value, the next field is filtered appropriately. This works as expected in configured screens, where users are guided to valid combinations.
However, we’ve found that the same dependency logic does not appear to be enforced when users edit those fields through a column set. Instead, users can see and select all available values, even if they would normally be filtered out on the screen.
This creates a few challenges for us:
- users can select invalid combinations
- data entry behavior is inconsistent between screens and column views
- we may need to disable column editing entirely for those attributes, which reduces flexibility and makes updates less efficient
From an admin perspective, it would be very helpful if column sets respected the same dependency behavior that already exists in screens.
