> For the complete documentation index, see [llms.txt](https://docs.zongsoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zongsoft.com/documentation/en/framework/externals/projects/closedxml.md).

# ClosedXml (closedxml)

ClosedXml project's capability scope, deployment products, integration entry and usage boundaries.

Business model integration Excel data archiving, extraction and template services are suitable for processes such as exporting business records, manually filling them in and then importing them.

| Item                  | value                                                                                     |
| --------------------- | ----------------------------------------------------------------------------------------- |
| source code directory | `externals/closedxml`                                                                     |
| main bag              | `Zongsoft.Externals.ClosedXml`                                                            |
| Companion theme       | [Spreadsheet and Template Extensions](/documentation/en/framework/externals/documents.md) |

## Deployment and Usage Portal

Append the main package to the existing host's [Deployment checklist](/documentation/en/references/deploy-files.md), and retain the plugin list, assembly and ancillary running resources in the package:

{% code title="Application.deploy (append fragment)" %}

```ini
[plugins zongsoft externals closedxml]
nuget:Zongsoft.Externals.ClosedXml
```

{% endcode %}

Match services in `Spreadsheet` format via [Core](https://github.com/Zongsoft/framework/tree/main/Zongsoft.Core)'s archive or template contract. The actual data service first provides its own descriptor, allowing the primary key, length and semantics in the mapping to enter the archiving process.

## Integration Steps

1. Export a small number of model records along the topic's generator example, checking column names, display formats, and field validation.
2. After manually modifying or appending records, use the same model to describe the extraction and compare the actual field values.
3. Cover empty tables, null values, long integers, dates and field changes, and then integrate business verification and writing.

For specific configuration, calling examples and related basic concepts, see [Spreadsheet and Template Extensions](/documentation/en/framework/externals/documents.md).

## Project Boundaries

{% hint style="info" %}
💡 The import location is an Excel Table. The spreadsheet name is `__{model.QualifiedName}__`. The worksheet name or ordinary area cannot replace it. When there are no summary rows, additional records will be extracted downwards within the spreadsheet column range, and comments should be placed outside the column band.
{% endhint %}

## Further Reading

[Browse extensions by project](/documentation/en/framework/externals/projects.md) · [Spreadsheet and Template Extensions](/documentation/en/framework/externals/documents.md) · [source code and project description](https://github.com/Zongsoft/framework/tree/main/externals/closedxml)


---

# 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.zongsoft.com/documentation/en/framework/externals/projects/closedxml.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.