Attribute Did Not Update While History XML Shows It Is Updated
Last updated on NOVEMBER 08, 2017
Applies to:Oracle BigMachines CPQ Cloud Service - Version 12.0 and later
Information in this document applies to any platform.
An attribute does not update as expected via a Web Service call, specifically, an updateTransaction SOAP call; however, the History XML shows that the attribute was updated.
To understand the symptom, this is a general use case:
- Web Service calls runs via 3rd party application such as Web Methods or similar. This calls an updateTransaction to update the attribute "textFromReconfigInbound_line" and the action to update is "save_line". Both are sub document type. The user associated with the updateTransaction call is "superuser".
- At the same time, a sales user opens the quote, unknowingly that a Web Service call is running for that specific quote. The sales user is called "admin003".
- Web Service returns a success response and the History XML logs the change.
- The user in (2) sees that the attribute retained the old value.
Below is the example History XML. Here it can be seen that the change_date are the same for "save_line", which is from the Web Service call and Open quote action, from the sales user, overlapped.
Transaction XML shows the quote did not update:
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 hundreds of Community platforms