Data Lookup Definition is not working on the Incident Form if an onChange Client Script contains "g_form.clearValue('cmdb_ci')" created on Matcher FieldDescriptionBuild information:Build name: LondonBuild date: 05-22-2019_1149Build tag: glide-london-06-27-2018__patch8-hotfix2-05-21-2019Issue Description:Data Lookup Definition is not working on the Incident Form if an onChange Client Script contains "g_form.clearValue('cmdb_ci')" created on any Matcher Field.Steps to Reproduce The Data Lookup entry "Priority Lookup" defined on the table incident.The value of the Priority is changed according to the value of Impact and Urgency.1. Log in as admin.2. Create an onChange Client Script on the Urgency field Incident table.Name: Test onChangeTable: IncidentUI Type: AllType: onChangeField name: UrgencyScript:function onChange(control, oldValue, newValue, isLoading, isTemplate) {if (isLoading || newValue === '') {return;}//Type appropriate comment here, and begin script belowg_form.clearValue('cmdb_ci');}3. Navigate to 'incident.do' to create a new incident.The default value of Impact is '3 - Low' and the default value of Urgency is '3 - Low'.The value of Priority is '5 - Planning'.4. Change the value of Impact to '1 - High'.The value of Priority is '3 - Moderate'.5. Change the value of Urgency.Expected behaviorThe value of Priority should be changed according to the Data Lookup entry "Priority Lookup" on the form.Actual behaviorThe value of Priority is always '3 - Moderate' on the form.Investigate Summary- This issue happens when API 'g_form.setValue('cmdb_ci', sys_id_of_cmdb_ci)' or 'g_form.clearValue(cmdb_ci)' in the onChange Client Script.- The issue happens on when setting or clearing the value of 'cmdb_ci'(Configuration Item).I tested Caller and Short Description, the issue doesn't happen.- This issue just happens on the form.Change the Urgency to '1- High'. The value of Priority is still '3 - Moderate' on the form.However, the value will be '1 - Critical' after the incident is submitted.WorkaroundThis issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In field to determine whether any versions have a permanent fix.Related Problem: PRB1351317