cancel
Showing results for 
Search instead for 
Did you mean: 

SAP CPI OData sender POST to Successfactors Upsert functionimport removes message body

tomvanrooijen
Participant
0 Kudos

Hi all,

I have to create a CPI OData Sender wrapper around some Successfactors recruiting OData services.
This more or less works fine but I am having issues with the upsert function (for candidates).

Creating a new candidate via the /Candidate OData works fine but Updating an existing one via Upsert poses some problems.
Upsert seems to be a functionimport in the Successfactors OData environment. I've updated my edmx for all the related entities and associations but it seems that Apache Olingo which CPI uses does not support a message body for function imports (using POST verb)

https://lists.apache.org/thread/ck4wy3zff5sj059l4owslbszzgv38w6n

Solution would be to pass all parameters via url but I cannot do that because for the outside world my OData sender has to mimic the behavior of the SF OData receiver which DOES support the json message body.

For now I have a workaround using a standard integration flow instead of an OData service but I also have to build in some deep inserts and I am not sure if the iflow workaround is still viable.
Does anyone recognize this issue that a POST to SF Upsert functionimport removes the message body in CPI?

Any workarounds or other tips for this issue?

Thanks,

Tom

Accepted Solutions (0)

Answers (0)