# Export Data
The Data Export node is used to export data. When this node is dragged onto the workflow, a popup window will automatically appear. In this window, you must select a list or list filter as the source from which you want to export the data.
Next, you can edit the properties to control the data export. The following properties are available:
| Property | Options | Description |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name** | | The name of the node. The name is automatically set and cannot be changed. |
| **Format** |
There are five options: – CSV – Excel (*.xlsx) – this is for the most recent Excel versions – Excel 97-2003 (*.xls) – this is for the older Excel versions – Json – XML
| Select how you want to export the data |
| **Source list** ‘ | Specify the list that is the source for the data export. This does not apply to `XML`or `Json`exports. | |
| **Filter by** | | If you need to filter the data that wil be exported, you can add an expression that defines that filter. |
| **Target field** | | Here you select the field where you want to store the exported data. This field has to be of the type `File` or `Text` (in case of `XML`or `Json`). |
| **Delimiter** |
There are four delimiters you can use: – Comma – Colon – Semicolon – Tab
| This property is only available (and needed) when the format of the export is CSV. This property defines which delimiter should be used to separate the data. |
| **Encoding** |
You can choose between 6 different character encodings: – ASCII – Windows-1252 – Latin 1 – ISO 8859-1 – UTF-8 – UTF-16 LE – UTF-16 BE
| This property is only available (and needed) when the format of the export is CSV. The property makes it possible to select the character encoding you want to use for the data export |
| **Include BOM** | | |
| **Sort by** | | When you click on this button you get to the Sorting popup where you can add expressions that make it possible to sort the exported data. |
| **Edit Columns** | | The `Edit Columns` button takes you to the Data Export Maps editor. |
This node has two exits:
* `Error`– this exit is used when the export produces an error;
* `Default exit` – this exit is used when the data export does not produce any errors.
#### Limit source to parent
This flag applies to nodes that work on nested lists and is enabled by default. The default behavior in WEM is that the parent row position is taken when working with lists. If the flag is switched off, all rows of the nested list considered in the operation. Switching off this flag is similar to the all keyword in WEM script. This setting is found in the properties pane on the right for the excel and csv export, the xml and json export has this setting in the edit mapping screen when the array item is selected (see below image).
#### Skip and Take
**For Excel/CSV**, Skip and Take are available in the properties pane. The **Skip** field defines how many rows to skip before the export starts, and the **Take** field defines how many rows to include in the export. Both fields expect a number.
**For JSON/XML**, Skip and Take work the same way but are found at the relevant node level inside the mapping editor, rather than in the properties pane. This means you can apply different Skip and Take values at each level of the mapping tree.
Skip and Take count rows within the selected list. When a filter is used as the source instead of a full list, Skip and Take count only the rows returned by that filter not the row positions within the underlying list.
#### Edit mapping
When you want to export to `Json` or `XML`, you need to specify a mapping to map the exported data to either `Json` or `XML`. This works the same as specifying the mapping for data import (see above for a description of how to create a mapping). The only difference is that the mapping will now be used to export data from your WEM application to `Json`or `XML` instead of importing data into your WEM application.
---
# Agent Instructions: 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:
```
GET https://docs.wem.io/platform/wemmodeler/flowcharts/export-data.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
