Loading the documentation…
Open a BI table when you need to change its name, work through its columns or point it at another table. This page covers the popup around that work: its tabs, the reports that use the table, saving and discarding your changes, what happens when someone else saved first, and replacing or deleting the table. The column settings themselves are described in BI table columns: labels, formats and summarization.
To create a table in the first place, start from the core-table picker (Create a BI table from a core table); this editor takes over once the table exists.
+{N} reports you can't open (+1 report you can't open for one) counts the reports that use the table but that you have no access to.While the list loads, the tab shows Loading report usage. When nothing uses the table it reads No reports use this table, and if the list cannot load it reads Couldn't load report usage: followed by the reason. The tab reads the list again each time you open it.
A report counts when one of its charts or report filters uses a column of the table. Bookmarks are not counted. This tab covers one BI table; the model's own Dependencies tab lists the reports built on the whole model (Check, document and trace a model).
The toast reads Bi table saved, or Column changes saved when only column settings changed. Column edits are saved before the name, and a failed column save stops the save with your changes still in place.
The name is required: an empty name blocks the save with Bi table name is required, and it also blocks tab switches. A save on a popup with no saved table yet reads Bi table is not saved yet.
Saves carry the version you loaded. When someone saved the table after that, the save does not go through and a dialog opens:
Reload replaces your edits with the version on the server. Overwrite keeps your version.
The Bi Table tab keeps three actions beside the name.
<names>. When reports use the table, the confirmation lists them and the button reads Delete anyway; see Check which reports will break. The popup closes when the delete finishes.Deleting cannot be undone: the table's columns, calculated columns and relationships go with it, and so do the report filters that target it. Measures are not deleted.
Until the table has been saved once, some surfaces in and around the popup ask for a save first:
Click Apply. It saves the name and the columns and keeps the popup open, and it appears while there is something to save. Finish saves and closes in one step, and simply closes when nothing is unsaved.
They appear only while there are unsaved changes; Finish is always in the footer. On Preview the footer is hidden entirely, so switch back to Bi Table to save.
You had unsaved changes. The Unsaved Changes dialog offers Save & Continue, Discard & Continue and Cancel; while the table is still being created only Save & Continue is offered. If the tab you are leaving has a missing required field, you stay on it and see a Validation Error notification instead.
The save opens This BI table was changed by someone else. Choose Reload to load their version and drop what you were editing, or Overwrite to save your version on top of theirs. The dialog waits for your choice.
It appears only if you can edit the semantic model. Ask an administrator for Edit DataPrism Semantic Models and edit access to the model; see Who can do what in DataPrism. When the tab is there but greyed out, the table has not been saved yet.
The popup's tab lists only the reports whose charts or report filters use a column of this table. The model's tab lists every report built on the model, whatever tables it reads.
No. Delete is enabled only once the table is saved; until then its tooltip reads Save the bi table before it can be deleted. Save the table first, then delete it.
Click Original table beside the name. It opens the bound table in the Lake or the Warehouse. It is disabled while that table loads (Loading table…) and when it cannot be resolved (Original table is unavailable).
The rename rewrites the measures that reference the table by name and re-checks them. It is refused when a live measure already has the new name (BI table name "<name>" collides with measure "<name>"; rename the measure first.), when row-level security custom SQL still names the table, and when more than 500 measures would need rewriting in one save.
No. Your edits stay in the popup until you click Apply or Finish. Until then the popup counts as having unsaved changes, so closing it asks you to confirm first.
Validation runs when you save, finish or switch tabs, and the error stays hidden until then. Once a check fails, the field reads Bi table name is required until the name is filled in.