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

Pagelist properties are mapped incorrectly

SA-89085

Summary

Pagelist properties are mapped incorrectly on using a JSON data transform when the response object contains a pagelist structure.


Error Messages

The Pagelist response is missing in the final json.


Steps to Reproduce

  1. Create a Service REST rule
  2. Create a JSON data transform in the Service activity to send the response in the JSON format 
  3. Send input to the JSON data transform in such a way that the input must contain properties on page as well as a pagelist on the page. All the direct properties on the page display in the JSON response where as if the page contains a pagelist with multiple entries, only the first entry is rendered in JSON Response
  4. Create separate JSON data transforms for page properties and pagelist
  5. Create another JSON Data transform 
  6. Form the output manually

Note:

  • If the input consists of pagelist only the JSON response works correctly
  • If the input consists of page with properties only the JSON response works correctly
  • If the input is page (properties +pagelist), JSON response returns only page( properties+1st entry of pagelist)


Root Cause



A defect in Pegasystems’ code or rules. 

Resolution



Perform the following local-change: 
  1. Use the Auto Mapping option in the JSON data transform   
  2. Remove the other fields via auto mapping which are not required
Suggest Edit

Published December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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