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

Inbound JSON message parsing fails in Connect-REST



PRException occurs when Connect-REST parses inbound JSON message. Dynamic of virtual properties does not work at runtime after deploying HFix-27308.

Error Messages

Caused by: Error mapping incoming response to .response_POST: cannot be null or blank. page: pyDataSource1504288586182.response_POST.groupResults(1). Details: Invalid value for aReference passed to, char)
From: (H6879FCF2984300FAC8C7E58699A226CF:...)
at com.pega.pegarules.integration.engine.internal.ServiceHelper.setInboundJsonValue(
at com.pega.pegarules.integration.engine.internal.ServiceHelper.setInboundDataValue(
at com.pega.pegarules.integration.engine.internal.ServiceHelper.mapInboundData(

Steps to Reproduce

  1. Install a new Pega 7.1.7 instance without any hotfixes
  2. Consume the JSON response file to create the REST integration related rules
  3. Open the data page and the response data transform rule used for mapping the JSON response to actual Pega properties
  4. Delete the properties created by the wizard and referenced in data transform under DataSource.response.
  5. Run the data page with the tracer. Pega creates the dynamic virtual properties in pyDataSource.response page based on the elements present in the JSON response
  6. Apply HFix-27308, delete the extract marker file and restart the application server
  7. Run the data page. The dynamic creation of virtual properties on pyDataSource.response page at runtime fails with the exception message

Root Cause

A defect in Pegasystems’ code or rules.


Apply HFix-35253.

Published December 6, 2017 - 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