Question
Pegasystems Inc.
JP
Last activity: 18 Apr 2019 0:35 EDT
How to parse two dimensional array JSON message in Pega Platform v8.1
Is there an OOTB way to parse two dimensional array JSON message in Pega Platform v8.1?
The in coming JSON message would looks like below.
{"twoDimensionList":[[{"name":"aaa"},{"name":"bbb"}],[{"name":"ccc"},{,"name":"ddd"}]]}
What would be the clipboard page structure for above JSON message?
How do I access the clipboard item, especially for the second level?
targetPage.twoDimensionList(1).???(1).name
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
US
I can't get this through REST Integration wizard and I've reached out to a Pega SME. I'll keep you posted.
Pegasystems Inc.
US
SME has responded and provided a suggested workaround. There are three ways to do this. The first two won't work with the attached sample JSON file.
A.) The data source wizard (including integration rule generation) currently fails, but we're working on the fix.
B.) There is a newer and way cooler wizard in app studio that is part of the Integration Designer we introduced in 8.1. It allows you to create a data type based on a rest endpoint (as well as lot more)– that works, but seems to have a minor bug in the generation – again the teams are investigating. This wizard will ask you to name the second array.
Note : for both A and B, the JSON DT we would produce is not perfect (although it would technically work for your use case at run time). The SME provided a workaround for these two - should you need to pursue either of these approaches.
C.) Use auto-map – Auto-map is a feature of json DT, and it offers the best performance. It simply assumes you want the complete JSON in clipboard, and that the clipboard has the right properties for it. This is what running automap on the example file attached:
SME has responded and provided a suggested workaround. There are three ways to do this. The first two won't work with the attached sample JSON file.
A.) The data source wizard (including integration rule generation) currently fails, but we're working on the fix.
B.) There is a newer and way cooler wizard in app studio that is part of the Integration Designer we introduced in 8.1. It allows you to create a data type based on a rest endpoint (as well as lot more)– that works, but seems to have a minor bug in the generation – again the teams are investigating. This wizard will ask you to name the second array.
Note : for both A and B, the JSON DT we would produce is not perfect (although it would technically work for your use case at run time). The SME provided a workaround for these two - should you need to pursue either of these approaches.
C.) Use auto-map – Auto-map is a feature of json DT, and it offers the best performance. It simply assumes you want the complete JSON in clipboard, and that the clipboard has the right properties for it. This is what running automap on the example file attached:
As you can see, when it doesn’t have a name, it just repeats the parent name, and it generates the entire structure just as you would expect.