SBL-DAT-00310: An error has occurred setting the field value.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.1.1 [19044]
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Sun Solaris 2.7

This document was previously published as Siebel SR 38-2112424241.

Symptoms

SBL-UIF-00299, SBL-APS-00201, SBL-DAT-00310

Hi Support Team,

We are upgrading our envirnoment from 7.5 to 7.8.
In siebel vanilla 7.5 if you navigate to Site Map -> Activities and then select an activity with empty "Start" field and try to set the "Alarm" field, then you will get the error as shown in the attached filed "Activity_Alarm_error_7.5.JPG". If you do the same things in siebel vanilla 7.8 you will get the error shown in the attached file "Activity_Alarm_error_7.8.JPG".

Our aim is to replace the 2. item in the error message in vanilla 7.8
" [2] An error has occured setting the field value."

with the previous one's message which is much more clear and tells to the user what needs to be done by saying which field should be filled.

"[2] Please enter a value for "Start" before entering a value for "Alarm". (SBL-APS-00201)"

is there a way to change the second item in the error message so that it will show the "Start" field should be filled first.

Thanks in advance.
P.S. in the attached 2 .jpg files you will see clearly what I mean.

Solution

Message 1

For the benefit of other users:

Original Issue:
Different Activity Alarm error messages are being displayed in Siebel version 7.5 and 7.8.

Solution:
The described behavior has been replicated against the Sample DB as follows:

- Select the Site Map > Activities
- Select an Activity where the Start field is empty
- Check the Alarm flag
> An error message is encountered. The error message is different in version 7.5 and 7.8:

- Siebel Version 7.5:
---------------------------
Microsoft Internet Explorer
---------------------------
[1] Wrong field values or value types detected in field Alarm. Please re-enter your field values. If you need additional assistance, please refer to the documentation.(SBL-UIF-00299)
[2] Please enter value for 'Start' before entering value for 'Alarm'.(SBL-APS-00201)

- Siebel Version 7.8:
Siebel
---------------------------
[1] Wrong field values or value types detected in field Alarm. Please re-enter your field values. If you need additional assistance, please refer to the documentation.(SBL-UIF-00299)
[2] An error has occurred setting the field value.

Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00310)

...

Message 2

...

These error messages are hard-coded and can not be altered. The Enhancement Change Request 12-ZBDIW4 (Different Activity Alarm Error Message from Siebel version 7.5) has been logged for this matter.

The current workaround is to use scripting to display a customized error message in Siebel version 7.8.

Keywords:
Alarm, Activity, Error Message

Thanks and Regards,

Applies to:

Siebel Tools - Version: 7.5.2.100 [15252] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.2.100 [15252]
Database: Oracle 8.1.7.3
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: Microsoft Windows 2000 Server SP 2

This document was previously published as Siebel SR 38-1187879421.

Symptoms

SBL-DAT-00310

Hello,

We have a requirement to create an Activity with an Alarm set to pop-up "as soon as possible" when a Service Request has its priority changed to "Urgent"

To that end I wrote the eScript shown below for the Service Request "BusComp_WriteRecord" event.

If I create a new Service Service Request in the "Service Request Detail View" and set the Priority to "Urgent", the script works fine and the required Activity is created.

If I create the Service Request in another view - e.g."Personal Service Request List View" or "Detail Service Request List View", I get the following error messages :

[1] An error has occurred setting the field value

Please continue or ask yout systems administrator to check your application configuration if the problem persists.

[2] Stack trace:
BusComp [Picklist Generic].Pick(), Built-in function
BusComp [Service Request].BusComp_WriteRecord(), Line 627


I commented out the code that set the "Pick" for the Alarm Lead Time but then I get the following error :

[1] The value '2/13/2004 11:56:49' for field 'Planned Completion' is required to be '>=[Planned]'.

Please enter a vlaue that is '>=[Planned]'
[2] Stack trace :
BusComp [Action].SetFieldValue(),Built-in function
BusComp [Service Request].BusComp_WriteRecord(), Line 670


Is there something wrong with my script or is there a workaround to this problem / requirement ?

Thank you.



function BusComp_WriteRecord ()
{


//Note - gPriority is set in the "BusComp_ChangeRecord" event
// and holds the Prioirty in entering the record

if (this.GetFieldValue("Priority") == "Urgent" && gPriority != 'Urgent')
    {

    var ActiveBO = TheApplication().ActiveBusObject();
        
    // Now create an Activity Alarm
    var HBSActionBC = ActiveBO.GetBusComp("Action")
    var bcActionTypePick
    var bcActionAlarmLeadPick
    var bcActionStatusPick
    
    with (HBSActionBC)
        {
        NewRecord(NewAfter)
        ActivateField("Type")
        ActivateField("Planned")
        A...

Cause

The following errors were received when running a script:

[1] An error has occurred setting the field value

Please continue or ask yout systems administrator to check your application configuration if the problem persists.

[2] Stack trace:
BusComp [Picklist Generic].Pick(), Built-in function
BusComp [Service Request].BusComp_WriteRecord(), Line 627

These errors were because ActivateField() was used before a NewRecord statement.

Solution

Moving the NewRecord() statement to occur after the ActivateField() calls, solved the issue.

Remember that ActivateField() should only ever be used before a scripted query. It adds fields to the list of fields to be returned in the next search you make in the script, it does not actually activate the fields like the BC property "ForceActive".