Unable to hard-code the party number in the request payload
(Doc ID 2613597.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Fusion B2B Service Cloud Service - Version 11.13.19.07.0 and later
Information in this document applies to any platform.
Customer is using Upsert-mode as true , in REST API integration to Oracle engagement cloud.
It is working fine, when provided a Party Number that already exists in OEC. which mean, it updates the record if there is record found with Party Number tag value.
However, in case when there is no matching record identified with party Number provided, it fails with an error
Below are the header and payload details.
"FirstName": "Test Contact 1207",
"LastName": "Test Contact 1207",
Attribute set for PartyNumber in entity PersonDEO failed
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