Import Management: AfterTransactionsPosted Notification & Subsequent GET Request Returns Out Of Date Data
(Doc ID 2738654.1)
Last updated on DECEMBER 24, 2020
Applies to:Oracle Fusion CX Sales Cloud Service - Version 11.13.20.07.0 and later
Information in this document applies to any platform.
In the environment it is an integration setup whereby the application informs a middleware of a create/update event using an AfterTransactionsPosted trigger in Sales cloud.
When the flow is used in UI, the trigger is firing after the data has been updated in the database.
When the flow is used in Import Management, seems the trigger is firing before the data was really updated in the database.
There is another integration where middleware perform a GET into Sales Cloud to retrieve the attribute level details, after the record was updated and after the triggered fired.
The After Transactions Posted includes a REST Web Service where perform a POST event and send the PartyId of the record being created/updated.
The middleware then uses the PartyId it receives to perform a GET Request.
When using Import Management, user noticed that the AfterTransactionsPosted trigger successfully notifies middleware but the GET response includes stale data and the attribute level updates are not the updates performed in the import.
The trigger is working fine, but seems it is not firing after the data has been posted to database, but it's firing before and it shouldn't.
If it should, it would return the last value that was updated and not the previous one.
It seems as though the AfterTransactionsPosted message is triggered before the other attributes are set.
When performing an update manually on the UI, the functionality works as expected.
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