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

Connect-REST JSON mapping issue with "invalid property name"



User is unable to map JSON response properties having special characters with PRPC properties.

Error Messages

Error mapping incoming response to .SecureMessagesList: The reference @total_records is not valid. Reason: invalid property name: '@total_records'

Steps to Reproduce

1. Create JSON property with special character. 
2. Map the response to observe the error.

Root Cause

The root cause of this problem is defect/misconfiguration in the operating environment. It is not possible to MAP if response property is with special characters such as "@".


This issue is resolved by HFix-22448.

In HFix-22448, below decision tables are added and code in service helper "getoutboundjsondata" and "setinboundjsondata" methods is updated.


Published June 23, 2015 - 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