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

• You're designing a custom iflow in CPI which uses a SuccessFactors OData V2 adapter to upsert information into SF;
• You're upserting an effective dated entity that contains the 'seqNumber' field, such as EmpJob;
• The 'seqNumber' field is not required as per the entity's metadata:
  
  
  
• 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=datetime'2020-08-25T17%3A51%3A38',userId='101010']</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-CUS , SF Boomi & CPI (HCI) Custom Content , LOD-SF-INT , Integrations , LOD-SF-INT-CPI , Standard SF to 3rd Party CPI (HCI) Content , Problem