Loading the documentation…
The Dependants tab in a table's popup lists everything that uses the table: other tables, Minds, transformations, decks, semantic models and API data-access grants. A Lake table's popup spells the tab Dependant; it is the same list. Check it before you change, drop or delete a table, so you know what your change can affect.
The same list powers the confirmation you see when you delete a table; see Deleting a table with dependants.
Open the table's popup and switch to the tab. For a Lake table, see Configure a table for the popup itself.
Each row names one dependant. A dependant can be:
slide 4 or slides 4, 7.The tab groups dependants by kind, in a fixed order: Dimension, Fact, Dictionary, Static, View, Transformation, Lake, Mind, WriteBack, Reference, Presentation and SemanticModel. Only the kinds in use appear. Each group shows a count of its entries, and the groups lay out in one to four columns, depending on the width of the window.
Rows for dependants you cannot access show a count instead of a name, like 2 presentations you cannot access; names are never shown, and the row is not clickable. The same pattern covers semantic models and Minds. Those dependants still use the table, so your change can break them even though you cannot open them. Ask their owners before you continue.
To change or remove the table itself, you need the Warehouse permissions described in Warehouse permissions and row-level security, or for a Lake table those in Who can do what in the Lake.
Click a row to open the object it points to: a Warehouse table or transformation opens its popup, a write-back opens its page, a presentation opens the deck, and a semantic model opens its page. A reference row opens the table it points to.
A pencil button appears on a row you can open when you point at it; its tooltip names the action for that kind:
| Kind | Pencil tooltip |
|---|---|
| Dimension | Edit dimension |
| Fact | Edit fact |
| Dictionary | Edit dictionary |
| Static | Edit static |
| View | Edit view |
| Transformation | Edit transformation |
| Mind | Start new chat |
| WriteBack | Edit write-back |
| Reference | Edit reference |
| Presentation | Open presentation |
| SemanticModel | Open semantic model |
Some rows do not open from the tab:
| What you see | What it means | What to do |
|---|---|---|
| Static Not Created with Please save the static table first to view its dependants | A static table's tab, before the table is saved. | Save the table first. |
| No dependants found with This table is not currently used by any downstream objects. | The check ran and found nothing that uses the table. For a static table, the line reads This static table is not currently used by any downstream objects. | Nothing; the table is not in use. |
| Failed to load dependants with Retry | The list could not load; the reason appears below the heading. | Click Retry; if it keeps failing, see Lake troubleshooting. |
| Dependants could not be determined | The DataPrism part of the check failed, so semantic models can be missing. The notice reads "DataPrism dependants could not be determined because the check failed. Acting on the assumption that this table is unused may be unsafe." The list still shows what the check could find. | Treat the list as incomplete and check the tab again later. |
A check that fails never shows No dependants found: a failure has its own message or notice. A check result is not kept from an earlier run; what you see is always the result of a fresh check.
The objects in the list keep reading the table. They can break when the table changes, is dropped or is deleted, until you fix them or redeploy the table. Review the list before a change that drops and recreates a deployed table (see Deploy a table) and before Drop or Delete on the Settings tab (see Deploy, run, truncate and monitor tables and Run, stop and troubleshoot loads).
Whichever way you start a delete, from the Settings tab, the tree (see Delete Lake items) or in bulk from Batch edit and organise, the same check runs first and shows this list. When something depends on the table, the confirm button reads Delete anyway. The check only warns, and only the table goes: the objects in the list stay behind. Deleting a table with dependants covers the dialog in full.
Removing a table needs Delete Warehouse Objects for a Warehouse table or Delete Lake Objects for a Lake table.
Some uses do not just warn; the server refuses the removal until you clear them:
The same protection covers single columns. A column that Minds use cannot be removed, and a column read by a data access grant is refused until the grant is revoked: Cannot remove column "…": ANY API connector "…" reads it through grant "…". Revoke the grant first.
Both. A Lake table's popup spells the tab Dependant; Warehouse and static table popups spell it Dependants. It is the same list of what uses the table.
Other tables (through a reference), Minds, transformations, Warehouse and Lake tables, write-back tables, presentations, DataPrism semantic models and ANY API data access grants.
Rows that stand for dependants you cannot access show a count instead of a name and never open. A Lake row and an ANY API data access grant row have nothing to open from the tab either. Every other row opens the object it names.
Two decks that use this table sit outside your access, so DataMind OS shows how many there are, never their names. The same pattern covers semantic models and Minds. Ask their owners before you change or remove the table.
Clicking the row takes you to the Mind. If you can open its settings panel, it opens on Sources; otherwise a chat with the Mind starts. The pencil (Start new chat) always starts a new chat, and the gear (View mind sources) opens Sources. The panel needs Create Minds, Edit Minds or Delete Minds, or View Training Cards. See Link data to a Mind.
The DataPrism part of the check could not run, so semantic models may be missing from the list. The notice reads "DataPrism dependants could not be determined because the check failed." It never means the table has no dependants. Check again later.
Click Retry to run the check again. If it keeps failing, see Lake troubleshooting.
No dependants found means the check ran and found nothing that uses the table. If the check itself failed, you see the undetermined notice or Failed to load dependants instead.
The static table has not been saved yet, so there is nothing to check: Please save the static table first to view its dependants. Save the table and open the tab again.
Yes. Deleting a table with dependants uses the same check and shows the same rows, including the counts for what you cannot access, before you confirm.
A live data access grant, a write-back table that uses it as its source, tables that depend on it, and Minds that use it or one of its permission groups. Each refusal names its cause and what to clear first; What blocks removing a table lists the messages.
An ANY API connector may read this table's data through a data-access grant. The row tells you the table has another consumer; nothing opens from it, and the grant blocks removing the table until it is revoked. See Data access grants.