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

Unable to parse XML content with colons in element names



You are unable to parse XML content that has colons in the element names.

Error Messages

Element name invalid.

Steps to Reproduce

Create a parse XML rule with a colon in the element name, for example:

<diffgr:diffgram xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">

Observe that this is
 mapped to an element named "diffgr:diffgram".

Root Cause

You must not have a colon in an element name.


This issue is resolved through the following Local-change:

When you configure a Parse XML rule, you name the node as (for the example above) diffgram and in the node properties, there is a node namespace field where you need to enter (for the example above) urn:schemas-microsoft-com:xml-diffgram-v1. This allows you to correctly name the element and give it a namespace

Published July 2, 2015 - Updated October 8, 2020

Was this useful?

0% 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