Question
TalkTalk
GB
Last activity: 26 Dec 2019 2:52 EST
response_GET pagelist/page issue
Hi, I am in a bit of a pickle with my REST connector requirements.
I have an endpoint, which returns me a list of results based on my request according to the following schema:
Hi, I am in a bit of a pickle with my REST connector requirements.
I have an endpoint, which returns me a list of results based on my request according to the following schema:
[ {"something" : "lalala"}]{"something" : "Invalid something"}Now, on a tracer I get an error saying that I get internal error that it is not able to map to response_GET.I understand that this is because response_GET is of type Pagelist rather than a single page.
Pegasystems Inc.
US
What version of Pega are you on? In 7.1.8 forward (and on 7.1.7 with HFix) you can map any property to the JSON element name and Pega will match by type. For example, you could have "fieldIdentifier" of type text and "fieldIdentifier" of type PageList.
In Pega, the first property "fieldIdentifier" would be of type text and the property name would be fieldIdentifier. If JSON element was not an array, it would get mapped.
The second one would have a unique property name such as "fieldIdentifierList" but under advanced, you would set up a pzExternalName "Property Qualifier" with "fieldIdentifier". If JSON element was an array, this second property would be used.
This solutions also helps in other ways : like when you have a JSON element starting with underscore. Pega property can't be named as such, so you create the property without the underscore and use pzExternalname to complete the mapping.
What version of Pega are you on? In 7.1.8 forward (and on 7.1.7 with HFix) you can map any property to the JSON element name and Pega will match by type. For example, you could have "fieldIdentifier" of type text and "fieldIdentifier" of type PageList.
In Pega, the first property "fieldIdentifier" would be of type text and the property name would be fieldIdentifier. If JSON element was not an array, it would get mapped.
The second one would have a unique property name such as "fieldIdentifierList" but under advanced, you would set up a pzExternalName "Property Qualifier" with "fieldIdentifier". If JSON element was an array, this second property would be used.
This solutions also helps in other ways : like when you have a JSON element starting with underscore. Pega property can't be named as such, so you create the property without the underscore and use pzExternalname to complete the mapping.
Another example, when there is named field in your inheritance path with a name you want mapped.
Virtusa
IN
Hi Paul,
We also have the same issue. The response is a list when the API is successful. For error cases, we get a single page as response.
So as suggested here, we created 2 properties named- 1)response_GET of type Page and 2)response_GETLIST of type PageList and pzExternalName = response_GET.
But it is not working. We are using version 7.2.2. could you please help.
Thanks in advance.
Pegasystems Inc.
IN
