When you need more than the chat's preview of a query result, ask Oda for the full result as a file. Oda writes the complete result into your workspace as a CSV or Excel file, and the chat keeps the preview and the note of where the file was saved. This page covers the file itself: where it goes, how it is named, and what can go wrong. For the Minds work behind it, see Company data, documents and reports; the tool-level detail is on Company data tools.
exports folder inside the chat's workspace folder.reports/ q3. csv. If you leave the extension off, Oda adds the one that matches the format, so reports/ q3 becomes reports/ q3. xlsx for an Excel export.. ., is refused before anything is sent, and the message asks for a relative path such as reports/ result. csv.When you do not choose a name, Oda builds one from the table the query reads plus the date and time of the save. A query over orders saved on 23 September 2026 at 09:05:07 becomes orders-20260923-090507..
Monthly Revenue reads monthly-revenue.datamind-export instead.orders-20260923-090507-2. csv. When no free name can be found at all, the export asks for an explicit name: Could not find a free file name for <base><extension>; pass file_name explicitly.. xlsx). Ask for the one you want in your request.A finished export reports where the file is. When an export cannot save a file, or stops partway, it says what happened. The messages below are the ones it can return.
| Message | What it means |
|---|---|
Saved the complete query result as <FORMAT> to <path> (<size>). | The export finished. The file is at <path> in your workspace and the rows were not loaded into the chat. |
file_name must not be empty; omit it to use the default name. | An empty name was sent for the file. Leave the name out to use the default one, or give a real name. |
Could not find a free file name for <base><extension>; pass file_name explicitly. | Every candidate name was already taken, so name the file yourself. |
<what> must stay inside the session workspace folder. | The path pointed outside the workspace folder. Use a path inside the workspace, such as reports/. |
<displayPath> already exists. | A file with that name is already there. Choose another name, or replace the existing file. |
This session runs in read-only mode, so datamind_export_query cannot save a file. | The chat cannot write files. Use a preview of the result instead, or switch the session to a mode that allows workspace writes. |
The export was cancelled and the partial file was removed. | The export stopped before it finished, and nothing half-written was kept. Ask again when you want the file. |
The export stopped before the file was complete (<reason>); the partial file was removed. | The export broke before the file was complete, and nothing half-written was kept. Retry, or narrow the query. |
In the chat's workspace folder. Without a folder in your request, it goes to the exports folder there, and the export reports the full path and the file's size.
A name built from the table the query reads and the time of the save, for example orders-20260923-090507.. A query with no clear table uses a name starting with datamind-export instead. If the name is taken, Oda adds a number to it.
Yes. Give a path relative to the workspace folder when you ask, such as reports/. If you leave the extension off, Oda adds the one that matches the format. The path must stay inside the workspace folder.
The file must stay inside the chat's workspace folder, so an absolute path or a path with . is refused with a message that asks for a relative path such as reports/. Name a place inside the workspace instead.
Two: CSV and Excel (.). Ask for the one you want in your request.
Excel workbooks hold at most 1,048,575 rows, so for larger results choose CSV.
Yes. Ask Oda to replace the existing file, and the export overwrites it. Without that, an export that lands on a name already in the workspace is refused, and the message offers another name or the replacement.
The chat runs in read-only mode, so it cannot write files and the export is refused before anything is sent. Use a preview of the result instead, or switch the session to a mode that allows workspace writes.
Nothing half-written is kept: the export removes the partial file and says so. Retry, or narrow the query.
No. The complete result goes into the file only; the chat keeps the preview and the note of where the file was saved.