---
title: PingDirectory suite of products 9.0.0.1 (March 2022)
description: Issue PingDataSync
component: pingdirectory
version: 9.3
page_id: pingdirectory:release_notes:pd_ds_rn_9001
canonical_url: https://docs.pingidentity.com/pingdirectory/9.3/release_notes/pd_ds_rn_9001.html
revdate: March 11, 2024
section_ids:
  issue-with-syncing-multi-valued-json-attributes-to-a-pingone-destination: Issue with syncing multi-valued JSON attributes to a PingOne destination
  added-support-for-synchronizing-data-to-custom-attributes-defined-in-pingone-destinations: Added support for synchronizing data to custom attributes defined in PingOne destinations
---

# PingDirectory suite of products 9.0.0.1 (March 2022)

## Issue with syncing multi-valued JSON attributes to a PingOne destination

Issue PingDataSync

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

Improved DS-36184, DS-45125 PingDataSync

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.