In case of bulk update of resource request from Integration using ODataAPI, Child object (Resource Onboarding Id) field values are flipping back to the previous one while Logs are being created in Grand child object with new value in Comments field.
SAP SuccessFactors HXM Suite
Concurrent update of the same records can lead to such issue.
Avoid the concurrent update of the same record. It does not mean you have to do all these in sequential one after another, however same records must not be updated concurrently.
For example, there are two records - P1 and P2. Each one of them has 10 records.
What is not allowed is when there are two or more threads/integration which are trying to update one or other records of P1 at the same time.
What you can do is (in the above example) two integrations - one updating all records for P1 and another thread can update all records of P2.
If there are multiple records like P1......Pn, you can have those many parallel updates, but each integration needs to ensure that P1 or Px is not updated by multiple integration.
MDF, MDF child objects, child objects, concurrent child objects, concurrent mdf, conccurent records mdf, odata api, odata api child records, odata api child object , KBA , LOD-SF-MDF-API , OData APIs & Integrations , Problem