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

Upgraded ParseXML parses Date value incorrectly



Post upgrading the ParseXML rule from PRPC 5 platform to PRPC 6.3 SP1, the ParseXML parses the date incorrectly.

The earlier ParseXML rule (PRPC 5 platform) parses the Date value correctly,

For example, the date: 2017-01-19 is parsed 20170119.

However, the upgraded ParseXML rule, parses the date incorrectly as 2017-01-19.

Error Messages

Not Applicable

Steps to Reproduce

Create a SwiftNet message to parse a Date value with the 2019-01-19 format.

Root Cause

The user upgraded the ParseXML rule from PRPC 5 platform to PRPC 6.3 SP1. The date was converted to the Pega internal Date format in the older rule. However, the upgraded version date did not convert to Pega's internal Date format. The was due to the changes Pega made to the Parse XML Design time and Runtime behavior.


Perform the following local-change:

Manually update the Parse XML Date property's XSD Node type to the Date property.

Published 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