Pega Send random field in Request JSON Requst payload on Connect-REST

General
, , , ,
1

Pega Send random field in Request JSON Requst payload on Connect-REST which was not defined Request data transform.

Refer the attached ss to reference the Request.bodyPOST which we set right before @baseclass pxCallConnector getting called. However when we looked at the actual payload which was generated in Pega Integration layer we have an additiona blank year filed was added. PFB.

“{“action_json”:
{
“event_id”:“E005436XXXXX”,
“year”:“2025”,
“include_names”:“TRUE”,
“year”:”“,
“varid”:”"
},
“action”:“GET_ALL_XXXXXXXXX”}"

Pega is adding and additional year filed when its generated request JSON. Not sure where Pega picks it up adding this filed additionally.

Screenshot 2024-12-27 090453.png
Screenshot 2024-12-27 090453.png449×170 4.87 KB

2

@AZARAHAMEDCan you attach Request data transform ss

3

@AZARAHAMED The issue of an extra blank year field being added to the request JSON in a Pega Connect-REST call usually happens when the same property is referenced multiple times in the Request Data Transform or when a blank value is explicitly set. Check your Request Data Transform to ensure .year is not defined more than once or assigned as blank (.year = ""). Also, review the Request Tab in the Connect-REST rule for any unnecessary property mappings. If using pxConvertPageToString, enable the second parameter as true to exclude empty properties from the JSON. Confirm the clipboard page just before the pxCallConnector call to ensure no unintended properties are present. If the property exists in the class structure but is not being set, Pega might auto-initialize it during JSON generation. Use Tracer to capture the payload step by step and identify where the extra field gets added. Adjust the Request Data Transform and mappings carefully to avoid this issue

4

@AZARAHAMED

We resolved the issue, by saving the same request data transform of the D Page.