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 response mapping error due to



User is on Pega 7.1.7,  a property "Name" in @baseclass that was created with Customer Process Manager (CPM) 7.12 installation.
User has a Connect-REST rule which complains about JSON response mapping failure due to conflicting @baseclass.Name property. User is getting the below error message in logs:

The property was of mode String while was expecting Page List mode.

Error Messages

The property was of mode String while was expecting Page List mode.

Steps to Reproduce

  1. Use Connect-REST Integration wizard in base Pega 7.1.7 to consume JSON response having "Name" element.
  2. Create a "Name" property in @baseclass.
  3. Call the Connect-REST rule from a data page or an activity. The JSON response mapping fails with error.

Root Cause

A defect in Pegasystems’ code or rules is identified as root cause of this issue. CPM 7.12 framework has a "name" property in @baseclass which conflicts with a property having same name when present within response data model generated by the Connect-REST Integration wizard.


Follow the below steps:
  1. Create a property "Name1" within the same class where "Name" property is present within the Connect-REST response data model.
  2. Go to Advanced tab of "Name1" property and set pzExternalName property qualifier as "Name".
  3. Delete the "Name" property which is present within the Connect-REST response data model and it was causing conflict with the "Name" property present in @baseclass.

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