> 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/openxml.md).

# OpenXml (openxml)

The capability scope, deployment products, integration entry points and usage boundaries of the OpenXml project.

Provides explicit workbook and cell operations, suitable for programs that require direct control of the spreadsheet structure. The archiving process of model records can also refer to the ClosedXml project.

| Item                  | value                                                                                     |
| --------------------- | ----------------------------------------------------------------------------------------- |
| source code directory | `externals/openxml`                                                                       |
| main bag              | `Zongsoft.Externals.OpenXml`                                                              |
| 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 openxml]
nuget:Zongsoft.Externals.OpenXml
```

{% endcode %}

Create or open a workbook directly using the SpreadsheetDocument wrapper in your project. The topic provides a short example of creating a workbook, writing to cells, and saving it.

## Integration Steps

1. Start by creating a worksheet and two cells, save and reopen to check the values.
2. Explicitly use the editable parameter when editing an existing file; the default open mode is read-only.
3. Verify the Chinese language, data type, required format and whether the file can be accessed again after release.

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 wrapper does not launch Excel, nor does it calculate formulas. Capabilities such as formula caching and charts should be verified according to the underlying implementation; the workbook created by the caller must be released in time to close the underlying file package.
{% 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/openxml)


---

# 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/openxml.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.