The Writeback table editor holds your edits until you save them. Apply saves the step you are on, and Revert brings the editor back to its last saved state.
The steps themselves are described on Configure a Writeback table and Map columns, and the editor's tabs on Create and edit a Writeback table. This page covers saving, unsaved changes and reverting.
The editor shows Revert and Apply while anything below differs from the saved state:
Before the save is sent, the editor checks the step. If the check fails, nothing is sent, and a Validation Error toast names what to fix:
| You tried to | The message reads |
|---|---|
| Move on from General before it is saved | Please complete and save the General configuration before continuing |
| Continue with required fields missing or a query that is not validated | Please complete all required fields and validate your query before continuing |
| Leave Columns with mapping errors | Please fix column mapping errors before continuing |
| Go back with changes that cannot be saved | Please complete all required fields before navigating |
| Finish with changes that cannot be saved | Please complete all required fields before finishing |
If the save is sent and fails, the message names the reason when the server provides it. The fallbacks read Failed to save write-back and Failed to save configuration. Your changes stay in the editor, so fix the cause and click Apply again. The full list, with a fix for each message, is on Writeback troubleshooting.
The step you are on. General saves the workflow and the source, and Columns saves the mapping. The other steps are read-only, and the editor moves you to the next step after a save.
They are shown only while the editor has unsaved changes. After a save or a revert, everything matches the saved state, so both buttons hide.
Every unsaved change goes back: the form fields, the query, the source selection and the column mapping. A mapping with no source comes back as unmapped, with the text type. To change something you already saved, edit it and click Apply again; Revert does not undo a save.
No. Revert restores the editor's whole unsaved state, not only the step you are on. Every change you have not saved goes back at once.
A General save is running. The footer controls are off until it finishes, so you cannot click Apply or move on in the meantime.
It depends on the source. When the table writes a query, the query brings its own columns, so saving General can map them and deploy the table without a separate mapping save. When it writes a whole source table, save the mapping on Columns. See Map columns.
No. A field that matches its saved value stops counting. An edited query is different: it counts until you save General or revert.
They stay in the editor. Fix the cause and click Apply again. The message names the reason when the server provides it; the fallbacks are Failed to save write-back and Failed to save configuration.