> 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/faqs/destinations/what-will-be-the-outcome-if-we-write-files-multiple-times-to-the-same-excel-destination.md).

# What will be the outcome if we write files multiple times to the same Excel Destination?

In the first run, it will always create a new file and write the data to that destination. In any subsequent runs, the user can choose how to write the file.

![AppendTo](https://docs.astera.com/projects/faqs/en/latest/_images/AppendTo.png)

If the *Append to File (If Exists)* option is checked, the file will be appended to the existing Excel file. If the option is left unchecked, the Excel file will be overwritten.

If the *Write to Multiple Files* option is checked, the data will be written at the dynamic file path provided by the user.

For more information, check out this video on [writing data to multiple files using a single destination object in Astera.](https://www.youtube.com/watch?v=lksmUfaWlsM\&list=PLmyM3TZtVUyKyvf75u9XUavn7T81avHrc\&index=4)


---

# 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://documentation.astera.com/faqs/destinations/what-will-be-the-outcome-if-we-write-files-multiple-times-to-the-same-excel-destination.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.