Deleting removes an item for good, and anyone it was shared with loses access. Delete one item from its menu, or tick several in the workspaces panel and delete them in one go. This page covers the confirmations, the results, and what a refusal means.
"{name}" will be permanently deleted.A report that was shared with you cannot be deleted; only the workspace it lives in can delete it. See Share a report.
Checking which reports use this model..Deleting "{name}" will invalidate N report(s) built on it. Opening a listed report closes the dialog and opens the report.In a bulk delete, tick a model's reports in the same selection so both go together. A model that a report outside the selection still uses is refused, and the refusal appears in the result described below.
This will permanently delete "{name}".Measures are not deleted with a BI table. A measure that can no longer run is marked invalid and left out of charts until you fix it; see Measures. The table's own editor has a separate Delete control with its own confirmation, described in Edit and save a BI table.
"{name}" and every folder inside it will be removed.Deleting cannot be undone, and a folder takes everything inside it: nested folders, and the reports and semantic models they hold. To take items out of a folder instead, drag them or use Move; see Move and copy items.
If a folder delete fails, a message titled Folder not deleted appears with the reason from the server.
Select folders, reports or semantic models to delete.Items to delete ({total}):, with a count for each kind, such as 2 folders, 1 report, 1 semantic model.Deleting a folder also deletes everything inside it. appears when folders are in the mix, A semantic model still used by a report outside this selection will be refused. when models are, and Anyone these were shared with loses access. always.Leaving batch mode clears the selection, and so does finishing a delete, whether or not everything went. Afterwards the result arrives as a message:
2 reports, 1 semantic model removed., or Nothing was left to remove. when a folder's cascade had already taken everything.{n} item(s) not deleted with {deleted} were removed. when some items were refused; the refused items open in the dialog described below.The result counts what actually went, including everything a folder took with it. Items that a folder in the same selection already removed are skipped, not reported as failures.
Refused items do not only arrive as a message; they open in a dialog titled {n} item(s) not deleted. Each row names the item and the server's own reason, and when no reason comes back the row reads The server refused to delete this item. Close the dialog with Close.
There is no retry, and none is needed: a refusal is a permission answer, so the same button would return the same sentence. Fix the cause instead: get the missing permission from an administrator, or ask the item's owner to delete it. The message table in Troubleshooting lists the wording of the common refusals.
| Permission | What it allows |
|---|---|
| Delete DataPrism Report | Delete reports you own. |
| Delete Others DataPrism Reports | The delete right for other people's reports. |
| Delete DataPrism Semantic Model | Delete models. |
| Manage DataPrism Workspaces | Create, rename and delete folders. |
A bulk delete asks for no extra permission: each item is checked with the gate a single delete would use, and a refusal names only the items you could not delete. For how permissions combine, see Who can do what in DataPrism; to change a role, see Roles and permissions.
They lose access. The confirmation states it: "{name}" will be permanently deleted. The bulk dialog repeats the same warning for a mixed selection as Anyone these were shared with loses access.
No. A report shared with you can be deleted only from the workspace it lives in: A report shared with you cannot be deleted. A share never covers deleting; see Share a report.
Because reports are built on the model you are deleting. Once the check finds them, the dialog lists them under Reports, warns that they will stop working, and changes the confirm button to Delete anyway. Read the list before you confirm.
No. The reports stay where they are and stop working, as the warning says. In a bulk delete, tick the reports with the model to take them together.
The confirmation spells it out: Items to delete ({total}): counts the selection by kind. A folder is ticked together with its contents, so the totals already include everything the cascade will take. If the totals are larger than you expected, cancel and adjust the ticks.
Because a refusal is a permission answer. Pressing the same button again would return the same sentence, so the dialog shows each item with its reason and a Close button. Check your permissions, or ask the item's owner to delete it.
Items that a folder in the same selection already removed are skipped, not reported as failures. The dialog that lists problems names only the items the server refused, with its reason.
Yes. The confirmations say the action cannot be undone; a folder also removes every folder, report and semantic model inside it.
On an item's menu, from its row in the workspaces panel or the actions button on its card on the home page. A report also has Delete under More actions in its header, and folders and BI tables have Delete in their row menus.