2967918 - Error when upserting record(s) into SuccessFactors without providing a sequence number - CPI SuccessFactors OData V2 Adapter

A client system (CPI, ERP, Postman, etc) is trying to upsert an effective dated entity that contains the 'seqNumber' field, such as EmpJob;

Still, if you do not provide the seqNumber in the upsert payload, the request fails with a response message similar to the following:

• "<d:status>ERROR</d:status>
  <d:editStatus>UPSERTED</d:editStatus>
  <d:message>bad valueString [] as part of keyString [seqNumber=,startDate=01/01/2025,userId='123']</d:message>"
  
  

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

insert, update, integration, interface, cpi, custom, required, nullable, cannot, can't, not, working, able, successful, unsuccessful, unable, failed, failing, fails, error, issue, message, throws, throwing, returning, returns, rejecting, rejects, problem, wrong, SF, effective-dated, effective, dated, seqNumber, api, odata , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT-CPI , Standard SF to 3rd Party CPI (HCI) Content , Problem