After you edit settings in Batch edit, use this page to save or revert them, read what each result message means, deploy a table from the grid and retry a row whose details failed to load. The Warehouse-wide message index is on Troubleshooting.
Revert drops every unsaved edit in both grids and puts the rows back to their saved values.
Two checks can hold a save back while table rows load their details:
Wait for the loading to finish, or retry the failed rows, then click Save again.
| You see | What it means |
|---|---|
| Saved, then All N item(s) updated successfully. | Every edited row was saved. |
| Partially saved, then N of M item(s) updated. | Some rows were saved and the rest failed. The failed rows keep your edits; open Failed Updates to see why. |
| Save failed, then No items were updated. Check the error bar for details. | Nothing was saved. Your edits stay in the grid, and the failure list shows the reasons. |
| No changes, then There are no changes to save. | The save found nothing left to send. |
| Saved, but the grid could not refresh, then The changes were saved. The rows will catch up when details finish loading. | Your changes were saved; only the grid refresh failed. Rows update as their details finish loading. |
After a clean save the grid reloads, and the saved rows load their details again.
When at least one row fails to save, a button with the number of failures appears in the grid toolbar, and its tooltip reads N item(s) failed - click to view. Click it to open Failed Updates.
Each entry in the list:
Rows that failed keep their edits. Fix the cause in the table's or transformation's popup, then click Save again. Rows that saved show their new values.
The Tables grid loads details for every row after it opens.
A row that has not loaded its details cannot be edited, and it blocks the save until it loads. Hover over Failed to read the reason (the fallback text is Failed to load table details), then click Retry to load that row again.
Deploying creates the table in the warehouse from its current definition; see Deploy, run, truncate and monitor tables for what deploying does.
After a successful deploy, the table stops showing Pending in the tree straight away, and its Status cell locks with This table is deployed and cannot be redeployed from here.
Deploying a table needs Add/Modify Warehouse Objects. See Warehouse permissions and row-level security.
Save and Revert stay greyed out until at least one cell differs from its saved value. Save also greys out while a save is running.
The grid needs each edited row's details before it can save its settings. If details are still arriving you see Still loading details; wait for the loading to finish, then save. If an edited row failed to load its details you see Table details not ready; click Retry in its Details cell, then save.
Some rows were saved and some failed. Rows that saved show their new values, and rows that failed keep your edits. Open Failed Updates from the grid toolbar for the reason on each failed row, fix the cause, then click Save again.
No. When nothing was updated you see Save failed, and your edits stay in the grid. Open the failure list from the toolbar button, fix the reason it gives, then click Save again.
The grid toolbar shows a button with the number of failures, and its tooltip reads N item(s) failed - click to view. It opens Failed Updates: each entry names the row, shows the reason, and offers Edit to open that table or transformation. A transformation's entry carries (transformation) after its name.
Your changes were saved; only the reload of the grid failed. The rows update to their new values as their details finish loading. If the grid still looks stale after that, close the popup and open Batch Edit again.
That row's details did not load, so the row is locked for editing until they do. Hover over Failed to read the reason, then click Retry to load the row again. A row without details also blocks the save.
Click Deployable in the table's Status cell, then confirm in Deploy table?. A success shows Table deployed successfully, and the table stops showing Pending in the tree.
No. A deployed row shows Deployed, and its Status cell is locked with This table is deployed and cannot be redeployed from here.
No. Saving applies the edits you made in the grid, nothing more. Deploying is separate: it happens only when you click Deployable in the Status column, or deploy the table from its own popup.
They are kept as a draft with that Batch Edit popup, so you can return to it and continue. The popup asks for confirmation before closing with unsaved changes, and a draft saved before a later update to the grid is discarded when the popup loads.