Idea Description
As a model builder, I want dependent dropdown rules to be enforced consistently across all data-entry methods, so that users cannot enter values that would otherwise be unavailable through the configured dropdown selections.
Example of Enhancement
I'll know this is successful when values that do not meet the dependent dropdown criteria are rejected regardless of how they are entered, including dropdown selection, manual entry, copy/paste, and bulk updates.
Benefit / Impact
We have identified a scenario where a line item formatted as a numbered list uses a dependent dropdown driven by a parent hierarchy. Access to valid selections is controlled through the dependent dropdown configuration and users only see valid options when interacting with the dropdown.
However, if a user pastes the internal numbered-list ID (e.g. #12345) directly into the field on a UX page, the value is accepted even when it would not be available as a valid selection through the dependent dropdown.
This results in inconsistent behaviour, where users are prevented from selecting a value through the UX but can still populate the same value via copy/paste. As a result, model builders cannot rely on dependent dropdowns to consistently enforce business rules and data validation across all methods of data entry.
Ensuring validation is applied consistently would improve data integrity, governance, and user confidence that configured dropdown restrictions are being honoured throughout the platform.
