Question
PerseusX Incorporated
SV
Last activity: 4 Oct 2024 16:58 EDT
Using Fast JSON Processing When JSON and Pega Clipboard Structures Differ
Hi,
I’m working on a Pega integration with a REST API. The API response includes a property called errors
that is a simple JSON object. In Pega, we have an out-of-the-box property named errors
that is a page list. During integration setup, the wizard created a new property errors2
(which is a single page as errors from JSON is a simple Object), and we used the Property Qualifiers option with pzExternalName
on the advanced tab to map the JSON errors
to errors2
, which works as intended.
We’re now aiming to improve performance by using the fast processing option for all of the services we consume. However, I understand that fast JSON processing requires an exact match between the JSON structure and the clipboard structure. When we use fast processing we get the next error:
'Caught unexpected exception mapping inbound data: For input string: "error" '
which I guess is caused due to the mismatch between the Pega OOTB property being a pagelist and the response "errors" being a simple JSON object
My question is: Is there any way to use fast JSON processing when the JSON property structure and the Pega clipboard property structure do not match? or Do we need to stick with standard mapping in this scenario?
Thank you for your help