---
title: JSON field constraints
description: Instructions for completing the service request form to define JSON field constraints.
component: pingoneadvancedservices
page_id: pingoneadvancedservices:task_summary_table:p1as_pd_json
canonical_url: https://docs.pingidentity.com/pingoneadvancedservices/task_summary_table/p1as_pd_json.html
revdate: June 27, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
---

# JSON field constraints

Submit your requests to define JSON field constraints through the service request form on the [Support Portal](https://support.pingidentity.com/s/).

## About this task

You can define a number of constraints for the fields included in JSON objects stored in values of a specified attribute type. For example, you can require that a field value is a specific data type, specify whether a field is required or optional, or restrict values of string fields to a predefined set of values.

Learn more about these values in [About managing JSON attribute values](https://docs.pingidentity.com/pingdirectory/latest/pingdirectory_server_administration_guide/pd_ds_manage_json_attr_values.html) in the PingDirectory documentation.

## Steps

1. Complete the following fields:

   * **Subject**: Enter a description of your request, including the action to be taken.

   * **Environment Type**: Specify the type of environment affected by this request.

   * **Proposed Change Window**: Specify the dates or times in which you want the work complete.

2. In the **Capability** list, select **PingDirectory service requests** > **JSON field constraints**.

3. In the **JSON attribute** field, specify the JSON attribute for which a field will be created.

4. Select the **Allow unnamed fields** option if you want to allow attributes that are not explicitly defined in the constraints.

5. In the **JSON field name** field, specify a field name to add to the JSON attribute

6. In the **Value type** field, specify the value type of the JSON.

7. Select the **Is required** option if this field should be required.

8. In the **Is array** field, specify whether the field should hold an array (required), can hold an array (optional) or cannot hold an array (prohibited).

9. Select the **Allow null value** option if you want to allow nun values in the field.

10. Select the **Allow empty object** option to allow empty objects in the field.

11. Select the **Index values** option to create an index for this field.

12. In the **Business Priority** list, select the appropriate description:

    * Change needed by deadline to avoid business impact

    * Change modifies existing functionality

    * Change adds new functionality

13. In the **Description** field, enter a description of your request.

14. If you are tracking your request within your organization, enter the tracking ID or ticket number associated with it in the **Customer Tracking ID** field.

15. To submit your request, click **Save**.
