> ## Documentation Index
> Fetch the complete documentation index at: https://docs.k16solutions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Export and troubleshoot worksheets

> Download worksheet results and resolve query, access, and editor problems.

Use worksheet exports for an approved point-in-time copy of a query result. Use blueprints, dashboards, or scheduled Lakehouse exports when the data must stay reusable or refresh automatically.

## Export query results

<Steps>
  <Step title="Run the final SQL">
    Run the SQL you intend to export and confirm its result. **Export** reruns the last executed
    SQL, including a selection-only run; unsaved edits after that run do not replace it.
  </Step>

  <Step title="Start the export">In the results toolbar, select **Export**.</Step>

  <Step title="Save the file">
    DataX prepares a CSV download. Large results can be split into more than one download URL and
    can use gzip compression.
  </Step>
</Steps>

If you need a governed entity instead of a file, use **Save as Blueprint** and follow [Create a blueprint](/datax/catalog/create-a-blueprint).

## Copy or download loaded rows

The table's **Copy / export** menu offers **Copy as CSV**, **Copy as TSV**, **Copy as JSON**, and **Download CSV**. These actions use rows already loaded in the result and the visible columns in their current order. They do not rerun SQL or fetch the complete warehouse result. The table's search does not narrow these copied rows.

Check the row count and visible columns before sharing a file. Use **Export** when you need the complete result of the last executed query.

## Resolve a query error

The **Results** panel shows the returned error and the SQL location when DataX can identify it.

1. Read the complete error instead of relying on the notification alone.
2. Check entity and column names against the schema explorer.
3. Confirm commas, aliases, quotes, and parentheses near the reported line.
4. Format the SQL to expose structural mistakes.
5. Run the smallest failing statement or selection.
6. Reintroduce joins, filters, and calculations one at a time.

When AI features are enabled, select the assistant fix action to request a proposed correction. Review the focused change or full suggested SQL, then select **Apply fix** only if it preserves your intent. Run the query again yourself.

<Warning>
  An assistant suggestion can change filters, joins, or calculations. Treat it as an editable draft,
  not as a verified result.
</Warning>

## Common problems

### An entity is missing from autocomplete

* Confirm that you are in the correct workspace.
* Search the [Catalog](/datax/catalog/browse) without filters.
* Check whether the entity is disabled or still a draft.
* Ask an administrator to verify your entity access.

### The query keeps running

Use the cancel action in the editor. Narrow the date range, select fewer columns, and remove unnecessary joins before trying again.

### Results are empty

Run each filter independently. Check date boundaries, null handling, exact category values, and inner joins that may remove unmatched records.

### Save fails

Open a personal copy before editing shared content. Confirm that the worksheet has a name and that you still have access to update it.

### Export fails

Rerun the query to confirm it still succeeds. Remove unsupported or unusually large values, then retry. If the query succeeds but the export repeatedly fails, record the worksheet name and error message for support.

### Open tabs disappear or show stale SQL

Save important drafts. Refresh the page, reopen the saved worksheet from **Explorer**, and confirm the displayed SQL before running it.