> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/files-and-tables/onedrive/best-practices.md).

# Best Practices

## Recommended setup

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Use consistent sheet names</strong></td><td>If you're importing from multiple sheets, keep their names consistent. When you rename a sheet in Excel, you'll need to update your data flow configuration to match.</td></tr><tr><td><strong>Keep headers in the first row</strong></td><td>Always ensure your Excel files have column headers in row 1. Coupler.io uses these to understand your data structure, and they make consolidation much easier if you're using multiple sheets.</td></tr><tr><td><strong>Combine sheets with Append</strong></td><td>If you have the same data structure across multiple sheets (e.g., regional sales data), use the Append transformation to stack them into a single dataset instead of importing them separately.</td></tr></tbody></table>

## Data refresh and scheduling

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Run a manual test first</strong></td><td>Always execute a manual run before setting up a schedule. This confirms the data flow works and shows you exactly what data will be imported — catching configuration errors early.</td></tr><tr><td><strong>Schedule around file edits</strong></td><td>If your Excel file is being edited regularly (e.g., by a team member), schedule imports during times when the file is typically not in use. This avoids importing partial or conflicting data.</td></tr></tbody></table>

## Performance optimization

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Use ranges for large files</strong></td><td>If your Excel file is very large, specify a cell range (e.g., A1:Z500) instead of importing everything. This speeds up imports and reduces the chance of timeouts.</td></tr><tr><td><strong>Remove blank rows and columns</strong></td><td>Clean up your Excel file before connecting — delete unused rows and columns, especially empty rows scattered through your data. This improves import speed and data quality.</td></tr></tbody></table>

## Common pitfalls

{% columns %}
{% column %}
**Do**

* Use the file picker to select files — it ensures you pick the right file and path
* Test with a smaller range first if your file is large
* Keep your source file organized with clear headers and minimal blank rows
* Reconnect your account if you see permission errors
  {% endcolumn %}

{% column %}
**Don't**

* Manually type file paths or IDs — always use the file picker
* Edit your Excel file while a data flow is running
* Leave blank rows in the middle of your data
* Assume sheet names are case-insensitive — Excel is picky about exact names
  {% endcolumn %}
  {% endcolumns %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/files-and-tables/onedrive/best-practices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
