Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Parse-XML fails to parse complex XML element



User is on Pega 7.2.1 and reported that Parse-XML rule fails to parse complex XML element. As an example the following elements have type associated with them in the XML data:

<suppliers type="array">
<id type="integer">3308</id>
<created-at type="dateTime">2017-03-13T22:46:48-07:00</created-at>
<updated-at type="dateTime">2017-03-13T22:46:48-07:00</updated-at>

Parse-XML fails to parse the value for the elements which are not mapped at all.

Error Messages

Not Applicable.

Steps to Reproduce

  1. Open Designer Studio > Integration> Connectors > Create REST Integration Wizard.
  2. Provide the endpoint URL of the sample XML to be imported.
  3. Select Get Method.
  4. Use override option to add the query string and header parameters.
  5. Mention Resource name as any name that matches with one of the complex nodes within the sample XML.
  6. Go to next step and click on Add a REST response. Pass the values for header and query string parameters as needed.
  7. Click next to go to Step# 4 and generate the rules.
  8. Run the generated Parse-XML rule and try to parse the XML response by selecting "Text to be parsed" option. We can see that the values for elements that has type associated with it are not parsed as shown in below example:


Root Cause

A defect in Pegasystems’ code or rules is identified as root cause of this issue.


Apply HFix-33635.

Published April 25, 2017 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us