> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v8/dataflows/sources/xml-json-file-source.md).

# XML/JSON File Source

Adding an *XML/JSON File Source* object to a dataflow allows you to read and transfer data from an XML or a JSON file.

{% embed url="<https://youtu.be/mWdoPPFjO0c>" %}

## **Getting XML/JSON Source Object**

1. To get an *XML/JSON File Source* from the *Toolbox*, go to *Toolbox > Sources > XML/JSON File Source*. If you are unable to see the Toolbox, go to *View > Toolbox* or press Ctrl + Alt + X.

<figure><img src="/files/8bRhZt0nJTnqHC0TCK7T" alt=""><figcaption></figcaption></figure>

2. Drag and drop the *XML/JSON File Source* object onto the designer.

<figure><img src="/files/ZFHW1AdWZrsWp6xmgzXr" alt=""><figcaption></figcaption></figure>

You can see that the dragged source object is empty right now. This is because we have not configured the object yet.

## **Configuring the XML/JSON File Source Object**

1. To configure the *XML/JSON File Source* object, right-click on the header and select *Properties* from the context menu.

<figure><img src="/files/ThxXVMH2N7sad65Ss8AB" alt=""><figcaption></figcaption></figure>

When you select the *Properties* option from the context menu, a dialog box will open.

<figure><img src="/files/icVhiLpxpebNk5vFRwzo" alt=""><figcaption></figcaption></figure>

This is where you can configure properties for the *XML/JSON File Source* object.

2. The first step is to provide the *File Path* and *Schema Location* for the *XML/JSON Source* object. By providing the file path and schema, you are building the connectivity to the source dataset.

<figure><img src="/files/3aIXYH4MPcqtWWDv3nUa" alt=""><figcaption></figcaption></figure>

* Check the *JSON Format* checkbox if your source file is a JSON.
* Check the *Provide Inner XML* checkbox to get the XML markup representing only the child nodes of the parent node.

{% hint style="info" %}
**Note**: In this case, we are going to be using an XML/JSON file with *Orders* sample data in the parent node and *Order Details* sample data in the child node.
{% endhint %}

<figure><img src="/files/izEnhvdFt3XEkrOtsqNa" alt=""><figcaption></figcaption></figure>

3. Once you have specified the data reading options in this window, click *Next*.

<figure><img src="/files/P2Rm5ozD2M1SQFuQRoCa" alt=""><figcaption></figcaption></figure>

On the *XML Layout* window, you can view the layout of your XML/JSON source file.

<figure><img src="/files/T8i4NNJWygn0JuSYeauv" alt=""><figcaption></figcaption></figure>

4. After you are done viewing the layout, click *Next*. You will be taken to a new window, *Config Parameters*. Here, you can define the parameters for the *XML/JSON File Source*.

Parameters can provide easier deployment of flows by eliminating hardcoded values and provide an easier way of changing multiple configurations with a simple value change.

{% hint style="info" %}
**Note**: Parameters left blank will use their default values assigned on the properties page.
{% endhint %}

<figure><img src="/files/DR3dvN1CYSNw3scsbKoi" alt=""><figcaption></figcaption></figure>

5. After you have configured the source object, click *OK*.

<figure><img src="/files/ctFY2cGq12mQP0GA1Q62" alt=""><figcaption></figcaption></figure>

You have successfully configured your *XML/JSON File Source* object. The fields from the source object can now be mapped to other objects in a dataflow.

<figure><img src="/files/voE2h9qVMtPQwMrrquf1" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.astera.com/astera-data-stack-v8/dataflows/sources/xml-json-file-source.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.