Question

Connect REST wizard not setting up response XML parsing correctly

Hello guys,

I am trying to integrate currency information of the European Central Bank to my Pega 7.3 app.

Currency information is provided here (http://www.ecb.europa.eu/stats/eurofxref/eurofxref-daily.xml) in XML format.

I used to connect REST wizard to generate the required rules.

When testing the information is received, but the currencies are not parsed correctly. The first one (USD) gets parsed the other ones are empty.

To reproduce it simply use the REST wizard with the above URL (request type GET) and let Pega build up the response parsing from the actual response.

As I see the Parse XML rule is set up properly.

Do you have any clues what the error's root cause might be?

Thanks.

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

Pega
November 16, 2017 - 11:38am

This data structure has the potential to confuse parsers, as it is difficult to determine what is "Cube" in scope while parsing this XML.

What does the resulting XML rule look like? Have you tried changing the appropriate "Cube" node to be a repeating node? It sounds like there may be a non-repeating node, resulting in only one value being captured.

November 16, 2017 - 8:47am
Response to HOULJ

It is a repeating node.

See the Parse XML that was generated below. We have checked it and it is correct.

After a lot of fiddling it turned out that setting the switchtooldassembler dynamic system setting to true (Pega-IntegrationEngine) Resolves the issue.

 

So in summary the old parser is able to parse the same XML using the same rules (if I am getting this right, not sure what that setting really does).

I think this can be considered as bug, pretty easy to reproduce, and should be fixed.

Pega
November 16, 2017 - 11:39am
Response to Gerg?T70

I'm glad that Dynamic System Setting worked for you.

It does appear that the "newer" assembler is misbehaving with this XML.