---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# JSON file import examples

# JSON file import examples {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of JSON File Import Examples

This document outlines how to import various types of JSON data into ServiceNow, detailing the necessary paths for each data row.
It emphasizes the importance of adhering to RFC-4627 standards and provides examples for different JSON structures, including simple arrays, nested arrays, and orphan arrays.
Show full answer Show less  

## Key Features

* **Path Requirements:** For JSON arrays, the path must include the root element twice (e.g., `/incidents/incidents`).
* **Child Array Support:** By default, nested arrays are not supported. This can be enabled by unchecking the 'Discard Arrays' option in the Data Source view.
* **Import Behavior:** The document outlines how enabling or disabling child array support affects the records created during import.

## Key Outcomes

By following these guidelines, ServiceNow customers can successfully import JSON data into their systems, ensuring data integrity and compliance with JSON standards. Customers can expect clear results based on the chosen paths and import settings, enabling efficient data management and usage within the ServiceNow platform.  
These examples demonstrate how to import various types of JSON data and the necessary
path for each row. JSON files that you import should follow these guidelines.
For step-by-step instructions on creating a File type data source see, [Create a File type data source](https://www.servicenow.com/docs/0l3nLt~ILh5izMZvEbNtcw "Create a File type data source record to define what data an import set should import.").

* For JSON arrays, the path for each row must specify the array root element twice, such as `/incidents/incidents`.
* JSON files should follow [RFC-4627](https://www.ietf.org/rfc/rfc4627.txt). For example, a single comma should separate a value from the following name. Names within an object should be unique.
* Predicates such as `@element`, `[index]`, or `text()`, as well as Axis such as children, siblings, or ancestors are not supported.
{#json-data-source-examples__ul_u43_kqc_m1b}

## Simple array

* Path for each row: `/incidents/incidents`
* Result: 2 records

{#json-data-source-examples__ul_bt4_33r_5x}In this example, the path for each row includes the array root node `/incidents` twice. This is necessary when importing an array.

    {  
       "source":"HI",
       "incidents":[  
          {  
             "number":"INC0000001",
             "short_description":"Can't read email"
          },
          {  
             "number":"INC0000002",
             "short_description":"Error loading XML file"
          }
       ]
    }

## Array in 2nd level

* Path for each row: `/problems/data/data`
* Result: 3 records

{#json-data-source-examples__ul_xh4_43r_5x}In this example, the path for each row includes the array root node `/data` twice.

    {  
       "problems":{  
          "id":"0",
          "data":[  
             {  
                "number":"PRBTEST001",
                "short_description":"testsd1"
             },
             {  
                "number":"PRBTEST002",
                "short_description":"testsd2"
             },
             {  
                "number":"PRBTEST003",
                "short_description":"testsd3"
             }
          ]
       }
    }

## Nested array

* Path for each row: `/problems/problems/data/data`
* Result: 3 records

{#json-data-source-examples__ul_yzl_t3r_5x}In this example, the path for each row includes the root nodes for both arrays twice, `/problems` and `/data`.

    {  
       "problems": [  
             {
          "id":0,
          "data":[  
                {  
                   "number":"PRBTEST001",
                   "short_description":"testsd1"
                },
                {  
                   "number":"PRBTEST002",
                   "short_description":"testsd2"
                },
                {  
                   "number":"PRBTEST003",
                   "short_description":"testsd3"
                }
              ]
           }
        ]	
    }

## Supporting child (nested) arrays {#json-data-source-examples__limited-support-child-arrays}

By default, import does not support child (nested) arrays. You can enable support by
unchecking the Discard Arrays check box in the Data Source view. The
following table describes different behaviors when enabling and disabling child array
support.

    { 
      "response":{
        "docs":[ 
          { 
            "id":"id_val",
            "childrenArray":[1,2,3],
            "anotherArray":[{"key1":"value1"}, {"key1": "value2"}],
            "elementWithArray":{"childrenArray":[1,2,3]}
          }
        ]
      }
    }

{#json-data-source-examples__table_apx_ct1_lhb__entry__3}

| Path | Discard Arrays Enabled | Discard Arrays Disabled |
|-|-|-|
| /response/docs/docs | Creates one record with the following columns and values: * Id : id_val * elementWithArray : {} {#json-data-source-examples__ul_rjv_tt1_lhb}Any arrays found in a record, such as childrenArray or anotherArray, are not created as columns in the import table. | Creates one record with the following columns and values: * Id : id_val * childrenArray : \[1, 2, 3\] * anotherArray : \[{"key1" : "value1"}, {"key1" : "value2"}\] * elementWithArray : {"childrenArray" : \[1, 2, 3\]} {#json-data-source-examples__ul_mzn_pt1_lhb} |
| /response/docs/docs/anotherArray/anotherArray | Creates two records, each with one column: key1. | Creates two records, each with one column: key1. |
| /response/docs/docs/childrenArray/childrenArray | Does not work and returns a Path should always refer JSON Objects error because the values in the array are not in a key-value structure. | Does not work and returns a Path should always refer JSON Objects error because the values in the array are not in a key-value structure. |
[Table 1. Child array behavior]

{#json-data-source-examples__table_apx_ct1_lhb}

## Orphan array

* Path for each row: `//`
* Result: 2 records
{#json-data-source-examples__ul_r3p_4l1_45b}

    [  
       {  
          "number":"PRBTEST001",
          "short_description":"testsd1"
       },
       {  
          "number":"PRBTEST002",
          "short_description":"testsd2"
       }
    ]

## Multiple elements instead of an array

* Path for each row: `/problems/problem`
* Result: 3 records

{#json-data-source-examples__ul_mds_djr_5x}  
Important:  
This format is not recommended. JSON files should follow RFC-4627, which states that names within an object should be unique. Use JSON arrays instead.

    {  
       "problems":{  
          "title":"2 problems",
          "problem":{  
             "number":"PRBTEST001",
             "short_description":"testsd1"
          },
          "problem":{  
             "number":"PRBTEST002",
             "short_description":"testsd2"
          }
       },
       "problems":{  
          "title":"1 problem",
          "problem":{  
             "number":"PRBTEST005",
             "short_description":"testsd5"
          }
       }
    }