SBL-DAT-00474: Invalid operation while not in update mode.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2.4 [19224] Cons Goods
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

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

Symptoms

SBL-DAT-00474

SupportWeb,

We have developed a new screen called “Retail Plan”. For Retail Plan functionality we have used the vanilla “CPG Promotion” BC. We need to implement the “Revise” functionality like we have in Quotes. For this revise functionality, we have used the vanilla “Revise” method. We have created a user property called “Revision Field” and value is set as “Revision Number. User Property “Revision Copy Field 1” ... has been used with necessary fields.

We have created a custom BC called “CPG Promotion.Revision Number (Sequence)” as it is in Quotes. Sometimes the record is getting the revised but we are consistently getting the following error:
- - -
Invalid operation while not in update mode.(SBL-DAT-00474)
- - -

We searched on the supportweb to know the possible causes of this error. But we didn’t get enough details.

Regards

Solution

Message 1

For the benefit of other readers:

# Issue:

We have developed a new screen called “Retail Plan”. For Retail Plan functionality we have used the vanilla “CPG Promotion” BC. We need to implement the “Revise” functionality like we have in Quotes. For this revise functionality, we have used the vanilla “Revise” method. We have created a user property called “Revision Field” and value is set as “Revision Number. User Property “Revision Copy Field 1” ... has been used with necessary fields.

We have created a custom BC called “CPG Promotion.Revision Number (Sequence)” as it is in Quotes. Sometimes the record is getting the revised but we are consistently getting the following error:
- - -
Invalid operation while not in update mode.(SBL-DAT-00474)
- - -

# Solution:

The following error was retrieved in the LOG file just before the error SBL-DAT-00474:
- - -
...
ObjMgrBusCompLog    Warning    2    0    2007-02-01 14:07:37    Field "Promotion Number" is not activated in BusComp "CPG Promotion".
GenericLog    GenericError    1    0    2007-02-01 14:07:37    Field Promotion Number is not activated in BusComp CPG Promotion.
ObjMgrSqlObjLog    Execute    4    0    2007-02-01 14:07:37    Begin: Execute SqlObj 'CPG Promotion.Revision Number (Sequence)' at 128162d0
...
- - -

The customized BC 'CPG Promotion' had well a field named 'Promotion Number' and this field was used as source field by a custom link 'RN CPG Promotion/CPG Promotion.Revision Number (Sequence)'.

[...]

Message 2

[...]

The field 'Promotion Number' had the 'Force Active' and 'Link Specification' properties set to FALSE and was not exposed in the view involved. This field was therefore not active when the revision occurred and caused the custom link to not work correctly.

The issue was resolved once the 'Force Active' property of field 'Promotion Number' was set to TRUE in BC 'CPG Promotion'.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2.1 [18353]
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

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

Symptoms

SBL-CSR-00418, SBL-UIF-00335, SBL-DAT-00305, SBL-DAT-00474

Not sure if this is a configuration issue or Siebel remote issue. I see the error when going into siebel remote administration -> trickle sync. If the list of mobile client is long enough(actually we only have about 50 so now), you will see this behaviour after you start changing things(like disabling trickel sync) while scrolling around.

I have attached a copy of the log file. We did not do any customization on that view.

Thanks,
Jonathan.

Solution

Message 1

For the benefit of others :
During the course of testing in the Standard Siebel application, version 7.7.2 [ 18325] ,
the following was the behavior observed :
In the Siebel Remote administration screen >Trickle sync view , there were around 40 records in the list applet and when we tried scrolling through the records time and again , we were faced with the error:

“ An error has occurred scrolling the Working Set .
Please continue or ask your Systems Administrator to check your application configuration if the
problem persists ( SBL-DAT-00305)”

But this error was not consistently reproducible and occurred may be once in 5 scroll attempts.
Sometimes after we clicked OK on the error we could go back to scrolling the records or sometimes refreshing the view got rid of the error and we were able to scroll through the records.

The Change Request #: 12-X22566 has been logged to address the above Product defect.

Thank you
Siebel Technical Support.

Applies to:

Siebel Tools - Version: 7.8.2 [19213] to 8.1.1.3[21219] - Release: V7 to V8
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Professional)
Version: 7.8.2 [19213]
Database: Oracle 10.1.0.1
Application Server OS: Microsoft Windows 2000 Advanced Server
Database Server OS: Sun Solaris 8

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

"" Checked for Relevance on 12-AUG-2010 ""

Symptoms

SBL-DAT-00474

I have a list applet with the following characteristics:
- based on a VBC
- it is a hierarchical list applet, so I copied the Catalog Admin Category List Applet to get the iconic controls and changed the underlying B.C. and List Columns

Here is the issue:
- I can navigate to the view/applet, click "New", add/select the data, and save a new record
- If I click "New" immediately after saving the 1st record I get the error message:
"Invalid operation while not in update mode. (SBL-DAT-00474)"
- Similarly, if I navigate to the view/applet and there is already a record displayed, when I click "New" I get the same error message.

Knowledge base gave me a few clues (e.g., invalid PickMaps) but nothing that helped resolve the issue.

When I click the "New" button (in either case above) I can see through the debugger that my VBC's "Init" and "PreInsert" methods both compete without error and return CancelOperation.

Any suggestions on how to diagnose or fix?

Cause

For the benefit of the reader customer was using Virtual Business Component “GHXR Exchange Connection (Ordered) VBC” to create new Records in Siebel Tables.. This Virtual Business Component is based on customer Business Service.

During testing it was found that user where able to just create one record at a time. If they try to create second record following error was shown

"Invalid operation while not in update mode. (SBL-DAT-00474)"

Solution

The root cause of this behavior was found to be in-correct setting on the VBC Business Component. For customer Business Component “GHXR Exchange Connection (Ordered) VBC” the property “Hierarchy Parent Field” was set to “Parent Org Id”. This property was removed and above error got resolved.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.13 [16275] FRA Fin Svcs
Database: IBM DB2 7
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM OS/390

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

Symptoms

SBL-DAT-00474

Dear Support,

following SR 38-2251508287 (4D: 948), we tested the fix you provided us in version 7.5.3.13 QF1D01.
When we create the first address on a Contact (or Account) record, it is defaulted to primary. When performing an undorecord right away, the Primary Address now remains checked.

We are happy with how it works, except that Siebel generates a WriteRecord, surely to commit the Primary Address Id.

To summarize, I select a contact record, I open the Personal Address MVG Applet, create the first address (which is defaulted to primary), close the applet, and click on UNDO RECORD. This calls a WriteRecord on Contact. We are fine with that, but we have some script on the Contact PreWriteRecord, and we noticed that if a SetFieldValue is triggered by Script, it fails, generating an error and cancelling the WriteRecord. Therefore, the Primary address is lost.

Attached, please find two web ex illustrating how it works in the following two scenarios:
- Performing an undorecord with NO script on the Contact PreWriteRecord
- Performing an undorecord simply after having scripted a "this.SetFieldValue("Email Address","Hello");" on the PreWriteRecord of BC Contact

In the second scenario, we notice that the field is updated, but if we put traces on the script, an error is raised when performing the SetFieldValue:

SiebelError: Op?ration non valide lorsque le mode de mise ? jour n'est pas s?lectionn?.(SBL-DAT-00474)
Error near no filename:5 [SetFieldValue()].
           from no filename:5 [BusComp_PreWriteRecord()]

Can you help us on this issue?

Thanks for your help

Solution

Message 1

For the benefit of other readers:

Customer is using QF1D01 on version 7.5.3.13 [16275] to resolve Change Request 12-ESFUG1. However, with this quick fix, customer notices that undoing an an action caues the loss of value for primary field as well as the field that is set in BusComp_PreWriteRecord event.

For example:
If there is a SetFieldValue statement (used on Email Address field) in BusComp_PreWriteRecord event of Contact business component, undoing the action in Contact business component causes the loss of value for Primary Address Id field and the Email Address field is not set too.

If try statement is used, the "Invalid operation while not in update mode" error is observed on SetFieldValue statement in BusComp_PreWriteRecord event in the log file.
ObjMgrLog    Error    4    2005-12-07 16:52:06    (SBL-EXL-00151) Error: SiebelError: Invalid operation while not in update mode.(SBL-DAT-00474)

Error near no filename:13 [SetFieldValue()].

      from no filename:13 [BusComp_PreWriteRecord()]

The following solution can be adopted if there is just a SetFieldValue statement. This can be used to avoid the loss of value of Primary Address Id field and Email Address field:

    try
    {
    this.SetFieldValue("Email Address","Hello");
    }
    
    catch(e)
    {
        TheApplication().RaiseErrorText(e);
    }
    
    finally
    {
        return (ContinueOperation);
    }

Change Request 12-193I1RR has been logged to address this.

Additional keys:
loss of data, SetFieldvalue fails, Update mode

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.2.218 [16087] DEU Fin Svcs
Database: IBM DB2 7.2 FixPack 3SA
Application Server OS: Microsoft Windows NT Server 4.0 SP 6a
Database Server OS: Microsoft Windows NT Server 4.0 SP 6a

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

Symptoms

SBL-DAT-00474

Hello,

In the standard configuration we get some problem with Activities. If you try to change some date fields respectively the alarm field. Please navigate to an existing action which has start and end date set and both are in the past. If you try to set the alarm flag then you get a valid warning that something is outside a valid time range. Then try to change an other field like comments and a confusing error (translated) 'Invalid Operation outside Update Mode' comes up. Similar things happen if you try to change the other dates and you get a warning. The error comes up but the data some times are stored.

The error occurs if and only if
a) I'm connected to the DB2 server database, no problems with the local database AND
b) I'm using the SADMIN account (no problem with other accounts)
SADMIN initially was configured as remote Client, so my impression is that the problem is somehow related to the transaction logging process.
Any further ideas (hopefully the trace helps). Please clarify.


Kind Regards

Solution

Message 1

For the benefits of other readers:

The behavior reported here has been reproduced in technical support using the following steps by step:

1) Create a Security Symbol in Financial Administration
2) Create an activity and assign to Symbol
3) Hide the security symbol and other fields of the same MVG in the Activity List Applet
4) Go to Financial Administration and delete your security Symbol
   - this step will also delete the entry in the intersection table S_ACT_PRDINT
   - but the primary id in the action remains
5) Go back to activities. The security MVFs are hidden, so the query does NOT clear the invalid primary product id
6) Try to update the activity (we have update the comment field).

Then you will see the following error message: Invalid operation while not in update mode.(SBL-DAT-00474)
We have opened the change request #12-MG332E to address this issue.

Thank you
Siebel Technical support.