---
title: "User interface description: XML/JSON window"
slug: "user-interface-description-xml-json-window"
tags: ["xml_json", "reference"]
updated: 2026-11-13T08:13:27Z
published: 2026-11-13T08:13:27Z
canonical: "help.dox42.com/user-interface-description-xml-json-window"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.dox42.com/llms.txt
> Use this file to discover all available pages before exploring further.

# User interface description: XML/JSON window

Since the behaviour and the settings of an XML or JSON data source can differ significantly, use this overview to understand the UI elements in the **XML/JSON** window.

## Data Source tab

| UI element name | UI element type | Requirement | Description |
| --- | --- | --- | --- |
| Name | text field | mandatory | Choose a descriptive name for your data source. |
| Http Header | button | optional | If the XML or JSON data is retrieved via a web service, additional authentication information may be required. This is configured via HTTP headers (e.g. tokens, credentials). |
| URL/XML/JSON | dropdown | mandatory | Supported HTTP methods: - `GET` to retrieve data - `POST` to send data |
| URL/XML/JSON | text field | mandatory | Enter a path or URL to an XML or JSON file, or choose a data field which contains an XML or JSON as text value. |
| Post Data | button | optional | This option only becomes available when the HTTP `POST` method is selected. This allows specific keys and values to be passed to the call, e.g., a request body. |
| Insert Data Field | button | optional | Select an XML/JSON data field as the basis for structuring, instead of an XML/JSON data source. |
| Username / Password | button | optional | For simple authentication using a username and password when accessing the server, instead of Http Header. |
| Enable Proxy Tunneling | checkbox | optional | Enables tunnelling through the configured proxy server when connecting to the XML/JSON data source. |
| Test | button | optional | Test your initialisation settings. |

## Initialisation & Fields tab

| UI element name | UI element type | Requirement | Description |
| --- | --- | --- | --- |
| Init from XSD/XML/JSON/WSDL | button | mandatory | Opens the **Init XML/JSON Data Source** window, where you - select and load an XML or JSON source - view its entire schema - select the element level from which data is to be read |
| SharePoint MultiValue Field/Apps | dropdown | optional | > [!WARNING] > Important > > Only relevant together for SharePoint and CE. Here you will find predefined initialisation options with useful templates for SharePoint app scenarios and CE scenarios (e.g. request body). These options help you to initialise common structures correctly and more quickly. |
| Element | text field | - | The element that data is read from in the XML/JSON structure. This field is pre-populated once you have selected the element in the **Init XML/JSON Data Source** window. |
| Test | button | optional | Test your initialisation settings. |
| Table columns |
| Read | dropdown | mandatory | Select how you want to read the individual XML elements that will be used as data fields: - `SubElement` To read the entire element (default value) - `Attribute` To read the element’s attributes - `Content` To display all content as text, without any XML structure - `XPath` To display specific values using a filter |
| XML Tag Name | text field | mandatory | Name of the subelement. This field is pre-populated with the original name of the xml tag. |
| Data Field Name | text field | optional | Define the name for the data field to be created. |
| Complex Type | checkbox | optional | Select the **Complex Type** checkbox if you want to retrieve all the sub-elements of an element. These sub-elements can be accessed via an additional XML/JSON data source; see [importing and structuring nested XML/JSON data](/help/docs/nested-loops). |