SetFieldValue Event Is Not Called From BC SetFieldValue Event With this.SetFieldValue
(Doc ID 2150381.1)
Last updated on NOVEMBER 22, 2019
Applies to:
Siebel CRM - Version 15.0 [IP2015] to 15.18 [IP2015] [Release V15]Information in this document applies to any platform.
Symptoms
ISSUE:
Calling in the BusComp_SetFieldValue Event a this.SetFieldValue Event of another Field from the same Business Component, the Event is not coming, just the PreSetFieldValue.
For example:
function BusComp_SetFieldValue(FieldName) {
switch (FieldName) {
case "Status":
this.SetFieldValue("Sub-Status", "");
return (CancelOperation);
break;
}
}
The Events are as follows: Set(Status), PreSet(Sub-Status), but the SetFieldValue Event of Field "Sub-Status" is not coming.
STEPS:
The issue can be reproduced at will with the following steps:
- Step 1: Open Service in Client
- Step 2: Change Field "INS Product"
- Step 3: Change Field "INS Area"
- Step 4: Change Field "INS Sub Area"
- Step 5: Change Field "INS Product" again
- Step 6: Check the trace file
function BusComp_SetFieldValue(FieldName)
{
switch (FieldName) {
case "INS Product":
this.SetFieldValue("INS Area", "");
TheApplication().TraceOn("", "Allocation", "CORBA");
TheApplication().Trace("Set: " + FieldName);
TheApplication().TraceOff();
break;
case "INS Area":
this.SetFieldValue("INS Sub-Area", "");
TheApplication().TraceOn("", "Allocation", "CORBA");
TheApplication().Trace("Set: " + FieldName);
TheApplication().TraceOff();
break;
}
}
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |