> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/export-table-data.md).

# Export Table Data

## Description

This function allows you to download data contained in application data tables to your computer or device. You can download this data using an XML format or comma-separated file format. Note: While this part is available in the Misc menu, you use it in form nodes and form-part nodes.

**Node Type:** This function is available in process nodes from the *Misc* dropdown menu but it must be used with form nodes and form-part nodes.

**Used With:** This function can be used with all framework types.

## Adding This Part

This part is available in the *Misc* dropdown menu in a process node, but you use it in form nodes and form-part nodes. To add this part, do the following:

1. Add a form node or form-part node to your logicnet.
2. Right-click on your node and select ***form details*** from the dropdown menu. This displays all of the tabs at the top of the editor field.
3. Click the ***Elements*** tab.
4. Click ***Misc*** and pull down to ***Export Table Data***. The system will put the part in the list of elements.
5. Double-click on the part to complete the editor fields.
6. Save your changes.

## Editor Fields

The *Export Table Data* function has the following fields.

| Field Name      | Description/Use                                                                                                                                      | Type/Options | Optional/Mandatory |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Data source     | This is the name of the data table to export.                                                                                                        | Text         | Mandatory          |
| File name       | This is the name the system gives to the downloaded file. If this is left blank the system will name the downloaded file the same name as the table. | Text         | Optional           |
| Export format   | This is the format in which the system exports the file.                                                                                             | Dropdown     | Mandatory          |
| Include headers | If you click this checkbox the system exports the table column names.                                                                                | Checkbox     | Optional           |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/export-table-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.