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 rule from a connect-soap does not parse



The SOAP response returned from an external .NET web service is not being parsed by the Pega generated Connect-SOAP and parse rules.

Error Messages

No specific error message.

Steps to Reproduce

Run PRPC’s Connector & Metadata generation wizard with the WSDL from the external .NET webservice.
Notice that after running the Connect-SOAP activity the returned SOAP response xml data is not getting parsed to the corresponding mapped clipboard page properties.

Root Cause

During course of detailed investigation it was found that the custom SOAP response xml data (X.xml) had a redundant blank namespace attribute defined under one of its element (NewDataSet). See screenshot highlighted below
<NewDataSet xmlns="">
                  <Table diffgr:id="Table1" msdata:rowOrder="0">
                     <Email>[email protected]</Email>


Remove the redundant namespace attribute from the external web service to confirm to the respective schema definition (.XSD). 

Published June 12, 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