> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/dragen-protein-quantification/after-counting-and-normalization/using-the-adat/compatibility-with-excel.md).
# Compatibility with Excel
While using the R and Python parsers is the recommended way to manipulate ADAT files, it is also possible to open and view them in Excel.
CSV version of the ADAT with final normalized counts is also provided under `adat/csv_format/` output directory.
### Opening an ADAT in Excel (Windows)
1. Open a blank excel workbook and browse for a file.
2. Confirm that "All Files (\*.\*)" are searchable.
3. Accept default parameters from Excel.
4. View ADAT in Excel!
###
### Opening an ADAT in Excel (Mac)
1. Open a blank excel workbook and select File > Import.
.png?alt=media)
2. Select the previously downloaded .adat file and then select **Get Data**.
3. From the Import window, select **Text file**, and then select **Import**.
4. Select **Delimited** (default) and then select **Next**.
5. Select **Tab** (default) and then select **Next**.
6. Select **General** (default) and then select **Next**.
7. Select the sheet and then select **Import**.
.png?alt=media)
8. View the ADAT in Excel.
---
# 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://help.bioinsight.illumina.com/dragen-protein-quantification/after-counting-and-normalization/using-the-adat/compatibility-with-excel.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)