Question

Issue in Connect Rest( ** Exception occurred while mapping incoming response to .response_POST.parts)

We are having requirment to hit external system to get the data by using Connect REST method.

In connect REST we are using POST method, request and response will be in JSON format.

Issue:** Exception occurred while mapping incoming response to .response_POST.parts

JSON Request in Pega

{

"country":"BRA",

"subDivision":"FRD",

"language":"ES-AR"

"parts":

[

{

"partNumber":"NF07063313",

"partType":"OWS"

}

]

}

Response should be mapped to response_POST.Parts which is not mapping.

Attached screen shot for more info

Please help me on this issue to resolve

Comments

Keep up to date on this post and subscribe to comments

August 24, 2018 - 4:12am

Hi Vishnu,

You can please try to map the response to a property on clipboard and parse the reponse using pxConvertStringToPage method later in data transform.

Thanks,

Divya Sri Padarthy

August 2, 2019 - 5:39am

Hi,

With the above mentioned approach you will still have the exception in data page as well log.

 pyErrorPage 
 Name   Value 
 pxObjClass   Embed-Error 
 pyStatusMessage   the HTTP response code of 400 indicated a client error. The response data may contain a reason. 
 pyStatus   Fail 
 pyHTTPResponseCode   400 
 pyStatusValue   Fail: Unexpected HTTP 400 Response code 

Pega
August 2, 2019 - 6:14am

Do you have the different response structure for success and failure case?

if yes than you can not map the data to page directly as response structure is not consistent .

you need to create a text property and save the incoming response to it and later based on the http status code of the response and map the data to clipboard using JSON data transforms

August 2, 2019 - 6:36am

Yes, for success the response structure is different. I tried to map in clipboard instead of JSON, that way we are able to map the property but still having the exception in log.

October 22, 2019 - 11:03am

I have the same issue. Do we know a solution for this?

October 22, 2019 - 11:19am

We found the root cause for us was the souce system was sending the response as single page for failure response but for success response it is sending in page list structure which was causing the problem.