My Oracle Support Banner

Merge SOAP Call On Custom Object Does Not Allow RecordName As Unique Identifier (Doc ID 2393975.1)

Last updated on MAY 02, 2018

Applies to:

Oracle Fusion Sales Cloud Service - Version 11.12.1.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.12.1.0.0 version, CX Integration

GBN: Merge SOAP call on Custom Object does not allow RecordName as unique identifier


As part of an integration flow (using ICS) I am creating or updating a Custom Object record using SOAP WebServices. In the scenario that the Custom Object record already exists we wish to simply update it, while when it does not yet exist we wish to create a new record.

I understood that this could be achieved with a single operation by using the MergeEntity or Merge operation, and that as of R12 we could use the RecordName attribute as an identifier for this call (as opposed to having to retrieve the Id attribute). This is laid out in the following Support Document: Update Custom Object Records By External Unique ID (Doc ID 2115955.1).

When testing this Merge operation call (attempting to update an existing record) however, I receive error messages stating that: BO-CASEINS_DUPLICATE_RECNAME: This value is a duplicate of another record's value (ignoring case)

Clearly the Merge operation is trying to create a new record - rather than updating the existing record (matching on RecordName) - and as such is getting error messages that it is not possible to create another record with the same RecordName since this has been defined as unique.

I've attached example request and response payloads for this. I've also attached a screenshot of the custom object and you can clearly see that RecordName has been defined as a unique field. For reference this Custom Object was created just two days ago.

Based on these errors it would indicate that the functionality described in Doc ID 2115955.1 has not been implemented on our environment yet, despite it being promised for R12.

Please can you confirm whether this is the case, and let us know why this logic has not yet been implemented? Is it possible to get this patched ASAP?


ERROR
-----------------------
BO-CASEINS_DUPLICATE_RECNAME: This value is a duplicate of another record's value (ignoring case)




STEPS
-----------------------
The issue can be reproduced at will with the following steps:

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot .

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!


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