UI Data Loss When A Field Is Readonly In List But Editable In Form
(Doc ID 2145852.1)
Last updated on FEBRUARY 03, 2019
Applies to:Siebel CRM - Version 188.8.131.52.16 [IP2014] and later
Information in this document applies to any platform.
Customer is reporting an issue with Ui Data loss when a field is readonly in List Applet but editable in Form Applet.
If you have a View which consists of a List and a Form Applet.
when a field is read-only in the List Applet, but editable in the Form Applet and the user enters data in the Form Applet, then does an implicit commit in the List Applet (e.g. click on another record), then the data entered in the Form Applet is entirely lost without any feedback to the user.
Fixing by making the field editable in the List Applet.
1. Using Siebel Tools, navigate to Applets.
2. Select Households List Applet and set the ReadOnly property of "Phone Number" List Column to TRUE.
3. Compile the Applet and launch Siebel Application.
4. Navigate to My Households view.
5. Update a Phone Number in the Form Applet, but do not commit the record.
6. Click back in the List Applet and do an Implicit Commit by clicking on the next record.
7. The phone number value that was modified in the Form Applet is lost.
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.|