Error SBL-DAT-00523 occurs when a script updates the current record through a second BC instance
(Doc ID 1127053.1)
Last updated on AUGUST 29, 2018
Applies to:Siebel Tools - Version 220.127.116.11 SIA to 18.104.22.168 SIA  [Release V7 to V8]
Information in this document applies to any platform.
""Checked for Relevance on 15-Oct-2014""
A script was created on a business component event handler for updating the current record. The script needs to update fields that have not been activated in the current BC instance. However, as the current instance exists in UI context, the programmer decided to update the current record through a new instance of the BC:
1. Get current record ID.
2. Save the current record.
3. Instantiate new BO.
4. Get a new instance of the current BC through the new BO.
5. In the new BC instance, query for the ID from step 1.
6. Update the returned record in the new BC instance as desired.
7. Save the record in the new BC instance.
A user accesses this BC through the UI and triggers the script. After that, the user modifies the record through the UI and tries to save it. However, this causes an error message:
"The selected record has been modified by another user since it was retrieved. Please continue. (SBL-DAT-00523)"
The script took care to save the current record before updating it through the second BC instance, so why is there an update conflict?
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
|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.|