Orlando - GlideForm methods in an onChange Catalog Client Script triggered by a Catalog Data Lookup Definition do not update target fields that have existing valuesDescriptionBuild information:<Builds that are known to be affected (e.g. June 2011 Preview 2)>Orlando EA Hot Fix 1<Builds that are known NOT to be affected (e.g. Calgary Patch 2, Hot fix 5) >MadridIssue Description:Orlando - GlideForm methods in an onChange Catalog Client Script triggered by a Catalog Data Lookup Definition do not update target fields that have existing valuesSteps to Reproduce Import update set of a simplified test case attached1. Locate the catalog item "Catalog Client Script Test."2. Search for and open the item "Catalog Client Script Test."3. Observe that, when the 'Set Directly from Data Lookup' field is populated with a default value, a value is set in the 'Changed by "Set Directly from Data Lookup"' field via a Catalog Client Script as intended. This would also work if there were no default value on the 'Set Directly from Data Lookup' field and the field's value were set for the first time via a data lookup definition.4. Change the value in the 'Please select a size' field. An alert message is displayed with the value that should be set. However, notice that the value in the variable 'Changed by "Set Directly from Data Lookup"' does not change. This field value should be updated by the Catalog Client Script "Set Indirect Variable" on the Catalog Client Script Test item.Expected behaviorGlideForm methods in an onChange Catalog Client Script triggered by a Catalog Data Lookup Definition should update target fieldsActual behaviorGlideForm methods in an onChange Catalog Client Script triggered by a Catalog Data Lookup Definition do not update target fields that have existing valuesWorkaroundThere is no workaround. This issue is fixed in Paris.Related Problem: PRB1388429