Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Data mapping limitations

Updated on April 6, 2022

There are some limitations when you are mapping JSON properties to REST response and request properties. The Data Object wizard displays an error message when a mapping is invalid.

  • If properties are in different nesting levels, they must be mapped to the same nesting level, for example, if a property on the left is in a sub-object, you cannot map it to a top-level property on the right. You can only map it to a second-level nested property.
  • Scalar properties must be mapped to scalar properties.
  • List properties must be mapped to list properties.
  • You cannot map two properties to the same property. If you try to do it, the last property mapped is used.
  • There are some limitations on types of properties that can be mapped to one another, for example, you cannot map a string to an integer.
  • The only supported date format is the Pega date format.

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us