Issue with syncing multi-valued JSON attributes to a PingOne destination
For multi-valued JSON attributes, you should not use JSON
attribute mappings when synchronizing data to a PingOne destination. When synchronizing JSON
data, you can use a direct attribute mapping if the data at the source server is
JSON. If the data at the source server should be assembled into JSON form, you
can define a constructed attribute mapping.
Added support for synchronizing data to custom attributes defined in PingOne destinations
Added support for synchronizing data to custom attributes defined in PingOne destinations. This includes multi-valued attributes and JSON attributes in the PingOne environment.
When defining attribute mappings for a PingOne destination, you can use direct attribute mappings for string to string or JSON to JSON synchronizations. If a string attribute at the source server should be stored as JSON in the PingOne environment, you should define a constructed attribute mapping in PingDataSync.