SAP Knowledge Base Article - Public

2628795 - OData entity when performing an upsert has an error "Save composite batch with same parent failed! Invalid navigation key!"

Symptom

  • You are using SFOdata entity to upsert the record
  • When upserting the record you face the error "Save composite batch with same parent failed! Invalid navigation key!"

Environment

 Successfactors

Reproducing the Issue

  1. Choose an entity in Odata API Data Dictionary which supports upsert functionality
  2. Create a request payload
  3. Setting the correct request headers, pass the payload to SFSF in a client tool (Middleware/REST client)

Cause

The root cause for this issue is because, the parent key is not existing for the record which is sent in the request payload

Resolution

This error can be resolved by first creating the respective record and then passing the exact external key(Business Keys) in the request payload and upsert the same

Keywords

  • Odata entity fails while upserting
  • Save composite batch with same parent failed! Invalid navigation key!
, KBA , "save composite batch with same parent f , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , SF Integrations - EC Payroll, Boomi/ HCI, API , Problem

Product

SAP SuccessFactors HCM Core all versions