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. 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.
Each row names one dependant. A dependant can be:
The tab groups dependants by kind. 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.
To change or remove the table itself, you need the Warehouse permissions described in Warehouse permissions and row-level security.
Click a row to open what it points to:
Some rows do not open:
Other tables (through a reference), Minds, transformations, Warehouse and Lake 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. An ANY API data access grant row has nothing to open 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.
To the Mind. If you can open its settings panel, it opens on Sources; otherwise a chat with the Mind starts. The panel needs Add Mind, Edit Mind or Delete Mind, or View Training Cards. Opening the dependant does not change your place in the Minds workspace. 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.
No dependants found means the check ran and found nothing that uses the table. If the check itself failed, you see the undetermined notice instead.
When a check covers several tables, at most 20 tables are checked in one go. If more were selected, the result says how many tables were skipped.
No. A check result is not kept from an earlier run, so what you see describes the moment it ran.
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.
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. See Connect any API.