Siebel Mobile: In Disconnected Mode a custom modified Unique Index is ignored
(Doc ID 2111646.1)
Last updated on FEBRUARY 28, 2018
Applies to:Siebel Mobile Applications - Version 184.108.40.206.9 [IP2014] and later
Information in this document applies to any platform.
Siebel Mobile Specific - on version: 220.127.116.11.13 [IP2014]
Service Mobile in Disconnected mode is ignoring the unique index
In Service Mobile Application > switch to Disconnected Mode > then navigate to certain custom View, and trying to create a second record there an error appears.
First record can be created but when trying to create the second record in the same view, this is the error seen:
"A record that contains identical values to the record you have created already exists.If you would like to enter a new record, please ensure that the field values are unique.(SBL-UIJ-00170)".
There is an User Key defined with a set of values, according to which, an unique 'Status Reason' value can be entered. However, that is not working in Disconnected mode. If trying to add any value for the 'Status Reason' it does not allow to save the record. In disconnected mode, in the application side log found the below error,
"WebDB - Execute, Sql Error Message: could not execute statement due to a constaint failure (19 UNIQUE constraint failed: ActivityStatusReason.ConflictId, ActivityStatusReason.ActivityId, ActivityStatusReason.Name, ActivityStatusReason.StatusReasonType) , ErrorCode : 6
BusComp - WriteRecord, A record that contains identical values to the record you have created already exists.
If you would like to enter a new record, please ensure that the field values are unique.(SBL-UIJ-00170)"
We have 5 User Keys values, in which one of them, ie. 'Status Reason' field is getting ignored. Please note, the field 'Status Reason' is extracted in Disconnected mode and has values.
It would be expected to see the User Key / UK index preventing to insert records with same fields' values.
The issue has the following business impact:
Due to this issue, users cannot control the data integrity of the records on the Mobile DB.
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