My Oracle Support Banner

SetFieldValue in BusComp_WriteRecord shows inconsistent results depending on how saving a record (Doc ID 2149230.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CRM - Version 15.7 [IP2015] and later
Information in this document applies to any platform.

Symptoms

The following escript code shows different behaviors depending how you save the record.

---------------------------------------------------function BusComp_WriteRecord ()
{
  this.SetFieldValue("target field", "target value");
}
---------------------------------------------------

Case1: Save a modified record by Ctrl+S or 'Save Record' in applet menu

-> The record is saved and then the 'target value' is set to 'target field'. If you step off the record or use 'Ctrl+S' or 'Save Record' again, then the 'target value' is saved.

Case2: Save a modified record by stepping off the record or using 'Edit'->'Change Records' in application menu

-> The record is saved and the 'target value' is discarded ('target value' is not modified).

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
Cause
Solution


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.