You have created an inbound integration using Integration Center and the Upsert performed by the integration fails with an error. You noticed that the error message doesn't indicate which exact record caused the error, as it can be seen in this example below:
User: UPSERT failed for the row with key: . Reason: The user is an inactive user, only the active user can be updated. Please activate this user first. The row will not be processed for subsequent entities
The "row with key: " statement presents a blank value.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
SAP SuccessFactors HXM Suite
- Integration Center
Integration Center will indicate which record caused the issue in the error message only if the OData API entity being Upserted is able to return the record key in the Upsert response. Some OData entities, when Upserted, will not return the business key of the Upserted record, like User entity for example. Some other entities does return the business keys of the Upserted records, like EmpJob or Position.
Integration Center will always present the same error message that the API has returned when the Upsert was performed. If we Upsert the User entity using Postman and it returns the error below, we'll be able to see the API response:
It doesn't mention any key, so Integration Center won't be able to mention it either.
However if we make an Upsert on Position, for example, and it return this error below:
We'll be able to see that a key is returned by the API, so Integration Center will mention it on its error message too.
ic, integration center, error handling, errors, key, record, index, value, upsert, fail, failing, not showing, successfactors, success factors, sf, odata, api, response, payload , KBA , LOD-SF-INT-INC , Integration Center , Problem