> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/system-basics/data-import-and-export.md).

# Data import and export

## Data import and export

Some screens allow users to export result data or import data from a file. Availability of these functions depends on the module and user permissions.

### Data export

Result data can be exported using the download icon usually located above the table on the right side. After clicking this icon, the system opens `File export`, where the user selects columns intended for export.

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2Fa5V9ZuiuIU9ddYFXwGEY%2F019.png?alt=media&amp;token=2adbb480-0ab2-49b3-afb9-d6174c2abd65" alt=""><figcaption></figcaption></figure>

1. Open a screen with a results table.
2. Use filters if needed.
3. Click the download icon above the table.
4. In `File export`, select the columns that should be included in the file.
5. Click the file format, for example `XLSX`, `XLS` or `PDF`.
6. After the format is clicked, the system starts downloading the file. The downloaded file name may include the export date and time, for example `exc_yyyy_mm_dd_hh-mm-ss.xlsx`.

### Data import

If a screen supports import, a button for importing data from a file is available.

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2FjN87xOox57nzho6JAFtW%2F020.png?alt=media&amp;token=a4079296-5e0a-455e-bb3a-23396fbfca09" alt=""><figcaption></figcaption></figure>

1. Click the data import button.
2. Select a file from disk.
3. After loading the file, check import parameters.
4. For each option, select the correct value from the dropdown list.
5. Start the import.
6. If the data and file format are correct, the file is loaded.

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2FNpzwQtxr5KO5kWjibcOS%2F021.png?alt=media&amp;token=cda4f3ed-60b9-4be2-9ed9-6b45fb4345ad" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2FyJuabVq4djNEikfYdUzl%2F022.png?alt=media&amp;token=70868046-1bac-485f-870b-187eec0328d2" alt=""><figcaption></figcaption></figure>

### What to watch for

* Import is available only on screens that support this operation.
* Export is available only on screens that provide the download icon above the table.
* File download starts after clicking the selected format in `File export`.
* The file format must match the requirements of the specific import.
* Before import, check file loading parameters.
* If import fails, check the file structure and required columns.

### Related pages

* [Filters and data search](/aquila-store-user-manual/system-basics/filters-and-data-search.md)
* [Working with tables](/aquila-store-user-manual/system-basics/working-with-tables.md)


---

# 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://docs.aquiladynamics.com/aquila-store-user-manual/system-basics/data-import-and-export.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.