We are trying to use the JSON data transform to directly map the JSON response from a service into a the data object of the data page, as suggested in the latest releases of Pega.
The problem is that we have noticed very big limitations, in particular there is no way to remap or change the input value before mapping it into the target property in the data model. For example the dates received must be mapped to a temporary string property before mapping them in the right field.
Do you have any suggestions? What is the suggestion from Pega to solve this limitations?
***Edited by Moderator Rupashree to add Capability tags***
I encountered a similar issue on a project.To solve this, we are mapping the JSON data as is in an Int class, then we have another data transform to map the Int properties into Work or Data properties.
If we take your example with the dates, in the Int class the dates would be stored in their original format into Text properties, then during the mapping into Work or Data class, you can change the date format to the Pega format and store it in Date or DateTime properties.