Skip to main content

 –

Data mapping limitations

Suggest edit Updated on August 16, 2021

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.
  • Scaler properties must be mapped to scaler 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.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us