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 not backward compatible, Pega properties renamed



After upgrading to Pega 7.1.6 from PRPC 6.3SP1, Rest Connector has backward compatibility issues, i.e. in Pega 7.1.6, Pega reserved properties (px, py, pz) are appended with "p_" causing existing Data grid to fail to render JSON objects in the UI.

Error Messages

No error message in the logs, but tracing the Connect-REST output, shows Pega reserved properties (px, py, pz) appended with p_", for example pxResultCount is renamed to p_px_ResultCount

Steps to Reproduce

1. Run the Connect-REST in Pega 7.1.6 to get page list of data.
2. Nothing is returned.

Root Cause

The root cause of this problem is defect/misconfiguration in the PRPC operating environment. Renaming Pega reserved properties (px, py, pz) appended with "p_" is an intentional change in Pega 7.1.6.


This issue is resolved through the following local change: use the ClipboardPage API calls instead of the JSON mapping feature of service/connector rules in 7.1 configuration to avoid using renamed Pega reserved properties. OOB functions, which will convert embedded pages into JSON structure are getPageAsJson() and getPropertyAsJson()

Published January 31, 2016 - 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