CPI: SuccessFactors OData V2 Receiver unable to get CamelHttpResponseCode

[former_member61388]

Hello, I need to do some logic in case the SuccessFactors OData V2 Receiver returns something different from 200. Too bad I can't get the http response status code from CamelHttpResponseCode in any way, I tried to enable all headers on entire flow with * from flow properties, I tried to enable all response headers with * in the adapter, I tried to copy it in another variable and to log it in many ways. But that header is never present!

Instead if I use the normal HTTP adapter I can see it and use it!

Thank you!

[Sriprasadsbhat · Accepted solution]

Hello Massimo,

I could see this behaviour only for POST operation ( where as with GET operation gives CamelHTTPResponse header in the response ).Please raise a ticket to LOD-HCI-PI with your finding so that somebody from developement team will revert back to you on this behavior.

Also for post operation you could use the field httpCode in the response getting from SFSF.Below is the sample upsert response for PerEmail.You can parse the response and store it as header/property using content modifier.

<?xml version='1.0' encoding='utf-8'?>
<UpsertResponses>
	<PerEmailUpsertResponse>
		<key>PerEmail/emailType=8448,PerEmail/personIdExternal=104024</key>
		<status>OK</status>
		<editStatus>UPSERTED</editStatus>
		<message>[Warning!] This record was not saved because there were no new changes compared to the existing record.</message>
		<index type="Edm.Int32">0</index>
		<httpCode type="Edm.Int32">200</httpCode>
		<inlineResults type="Bag(SFOData.UpsertResult)"/>
	</PerEmailUpsertResponse>
</UpsertResponses>

Regards,

Sriprasad Shivaram Bhat

[former_member61388 · Accepted solution]

Thank you very much sriprasadshivaramabhat, I will open the ticket at once!

And thanks for the workaround 🙂