Reference field is not filtered when the Dependent field is populated by a Client Script Description<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Reference fields are not filtered when a Dependent field is populated by a Client Script when List v3 is enabled. For instance, if we have: FieldA which is populated by a onChange Client Script FieldB which is a reference field with a Reference qual condition and its Dependent Field is FieldA. Once FieldA is populated by the client script, the reference field does not show the values depending on the reference qual condition. It shows all the values without filtering. If the value for FieldA is entered manually, then FieldB displays the right values. Release Jakarta and Kingston. Environment List v3 is enabled. Cause PRB1210372: Dependent field not honored when set via client script Resolution No workaround is available, except disabling List v3. PRB1210372 is fixed in the following available versions: London Patch 5,Madrid Patch 1,London Patch 6,London Patch 4 Hot Fix 2. Additional Information Please refer to the below KB article for steps to upgrade if required:https://support.servicenow.com/kb_view.do?sysparm_article=KB0541128