SOA 12.2.1.3 To 12.2.1.4 Upgrade - Salesforce Adapter Runtime Behavior Different (Doc ID 3054611.1)

Last updated on NOVEMBER 18, 2024

Applies to:

Symptoms

On : 12.2.1.4.0 version, Technology Adapters

ACTUAL BEHAVIOR
---------------
SOA 12.2.1.3 to 12.2.1.4 Upgrade - Salesforce Adapter runtime behavior different

We recently upgraded from SOA 12.2.1.3 to 12.2.1.4 leveraging the reduced downtime approach as documented here: https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.4/fupss/reduced-downtime-upgrade-process.html#GUID-1261BC57-65FE-4AB9-8B84-E42906BF1666

Our upgrade was successful and servers started successfully, but we are noticing a severe difference in runtime execution of Salesforce Adapter causing our composites to fail, we are not sure if there is a patch to ensure behavior in 12.2.1.4 is backward compatible.

On surface our main observation is that Adapter is enforcing allorNone default as TRUE instead of false as in 12.2.1.3, due to this, when a Adapter call is made, it is rejecting entire payload instead of just failing the requisite particular record in the input

Attaching the example of how 12.2.1.3 input payload and behavior v/s 12.2.1.4 where entire payload is rejected instead of just the faulty record.
 

EXPECTED BEHAVIOR
-----------------------

To continue the flow though a record fails

12.2.1.4 post upgrade if any one of the
Exception occurred when binding was invoked.

Exception occurred during invocation of JCA binding: "JCA Binding execute of Reference operation 'upsert' failed due to: DUPLICATE_VALUE: Duplicate external id specified: srf.
The invoked JCA adapter raised a resource exception.
UnexpectedErrorFault
DUPLICATE_VALUE: Duplicate external id specified: srf

  

Cause

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