Every company-data task in Company data, documents and reports goes through the Minds of your DataMind OS, with your own account and permissions, so Oda never sees more than you can. Behind the scenes, a fixed set of company-data tools asks the Minds, reads their tables, runs read-only queries and searches their documents. This page covers those tools, their limits and the messages they return.
| The tool | What it does |
|---|---|
| Finding a Mind | Lists the Minds your account can use, with their type and description. Oda asks the one or few Minds that fit the task, not every Mind. |
| Asking a question | Sends a business question and waits for the answer. A follow-up continues the same conversation with the same Mind. |
| Answering back | When a Mind pauses with a question, Oda brings it to you and passes your answer back to the Mind. |
| Cancelling | Calls off a question that is no longer needed. |
| Reading the structure | Lists the tables a Mind can read, and the columns of one of them. |
| Checking numbers | Runs a read-only query over those tables and shows a preview of the result in the chat. |
| Saving full results | Saves the complete result of a query in the chat's workspace as a CSV or Excel file. See Export query results. |
| Documents and definitions | Searches a Mind's knowledge base for documents, business definitions and instructions. |
These tools are the only route from Oda to your company's data. Their reach is fixed: Oda cannot change Minds, dashboards, users or permissions, and it cannot write to company databases. Those changes stay in the DataMind web app.
The company-data tools appear only while your account holds the Use Minds from DataMind Oda permission. While it is missing, none of the tools are offered, and the message reads Minds are not available for this account. If your account can reach no Minds at all, Oda reports No Minds are available to this account. and tells you to ask an administrator for access to a Mind.
Permission changes follow your account: a grant or a removal takes effect the next time your account loads in Oda, for example at the next sign-in. Ask your administrator for the permission; Manage DataMind Oda for your company shows where it is given.
A query preview ends with a line that tells you what came back:
The query returned no rows. The query ran and found nothing.57 rows returned. The preview holds that many rows.A Mind can pause before it can finish: it asks for something it needs. Oda answers only when your own request already makes the answer clear; otherwise it brings the question to you in the chat and waits. Your answer goes back to the Mind, and the answer completes. The question arrives like any other question Oda asks; see Answering Oda's questions.
Two rules hold whatever the question:
Not every question ends with an answer in words. The chat shows what happened:
The Mind job was cancelled, possibly from the DataMind web app. The job stopped before it finished. Ask again if you still need the answer.The Mind did not finish within <minutes>, so the job was cancelled. The answer ran too long; narrow the question, or try again later.The Mind could not finish this job: <reason>. The Mind stopped with an error. The reason comes from the Mind, or reads DataMind reported no reason when it reports none.server restarted as its reason. Ask again to get the answer.The Mind finished without a text answer. The Mind completed but wrote no answer text. When it also saved results, Oda adds The Mind also produced <n> artifact(s), visible in that conversation in the DataMind web app. The results stay on the server; use them from the DataMind web app.To call a question off yourself, ask Oda to cancel it; the chat reports Cancelled Mind job "<id>". A cancelled question stays cancelled even if its work finishes afterwards: the late result is dropped.
At most four at a time, across everything Oda is doing. Further asks wait their turn in order, and a question cancelled while it waits never reaches your DataMind server.
Up to an hour. An answer can take minutes; a question that runs longer than that is cancelled, and Oda suggests a narrower question or a retry.
Yes. Ask Oda to cancel it, or stop the task it belongs to. The chat reports Cancelled Mind job "<id>".
The job stopped before it finished. The message says it was possibly cancelled in the DataMind web app; it is also cancelled when it runs past the time Oda waits, or when the task it belongs to is stopped. Ask again if you still need the answer.
At most 50. For the complete result, ask for it as a file; see Export query results.
A long cell is shortened to 200 characters in the preview. Save the complete result as a file if you need the full values.
Oda answers it only when your own request already makes the answer clear; otherwise it brings the question to you and waits. Answer it and Oda passes your answer back, then shows the finished answer. Oda never answers a request for passwords or keys; it cancels such a question and tells you.
The chat reads The Mind finished without a text answer. When the Mind also saved results, Oda says they are visible in that conversation in the DataMind web app; those results stay on the server.
Your account does not hold the Use Minds from DataMind Oda permission. Ask your administrator for it; access is picked up the next time your account loads in Oda, for example at the next sign-in. Manage DataMind Oda for your company shows where it is given.
8 by default, and never more than 20. Each result carries its title and a snippet from the Mind's documents.