My Oracle Support Banner

Custom Integration Component User Keys And Custom User Key Fields Are Not Being Used During Inbound REST PUT (Upsert) Method Call After Siebel 20.6 PatchSet (Doc ID 2725472.1)

Last updated on SEPTEMBER 29, 2021

Applies to:

Siebel CRM - Version 20.6 and later
Information in this document applies to any platform.

Symptoms

When testing on Siebel 19.8, it was possible to send in a PUT request (PUT for Upsert operation) and it would use a custom user key defined to find the record and update the existing record.

However, after applying 20.6, the same PUT request no longer uses any of the custom user keys and only uses the Id field value.


The behaviour occurs as follows:

1. Send a request for Inbound REST to create a new product record.

2. Send a second request for Inbound REST for the same record that was created, provide the field name used in the User Key and also provide a new value for another field that should be updated.

3. The second request fails to create a new record and indicates that the record is being created with same values as an existing record, violating the user keys uniqueness.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.