While using UpdatedNodes with OrderDataUpdate or UpdateOrder It Is Always Overwriting the Old Value
(Doc ID 1535439.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Communications Order and Service Management - Version 7.2.0 and later
Information in this document applies to any platform.
From OSM Developer Guide Documentation in section 4-11, it states that for UpdateOrder UpdatedNodes interface, the system Provides the ability to update the order by supplying only the nodes to be updated (elements added or changed).
What is the condition for UpdatedNodes to add new node or Update existing Node?
When OrderDataUpdate with UpdatedNodes operation is used to add a new Node, the new value overwrites the old value. Is there any way to configure the system to not update, instead, to create a new node?
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