A Writeback table receives rows from DataMind OS and writes them into a table of a destination. Configure it to set where its rows come from and which workflow runs it. Use this page for the General step, the Dependencies step and the Preview tab.
To open the editor and for its tabs, steps and saving mechanics, see Create and edit a Writeback table.
The Target section shows the name of the table in the destination. You cannot change it here.
| Setting | What it does | Default |
|---|---|---|
| Table Selection | On: the table takes a whole deployed Lake or Warehouse table. Off: the table takes the result of a query. | On for a new table |
| Table Type | Chooses which tables Table Name offers: Lake or Warehouse. | Lake |
| Table Name | The deployed table to write. Options follow the Table Type and are sorted by name. Type in the list to search. | Shows Select a table |
| Workflow | The workflow that runs this table. Apply saves General only when one is chosen. | The destination's (Standard) workflow, set at import |
On a RabbitMQ destination, General also shows a Publish Window. See Publish to RabbitMQ.
To use a Lake or Warehouse table as a source, it must be deployed. See Configure a table.
When Table Selection is off, the editor tile shows these controls:
If the query is empty, Validate stops with Query cannot be empty. When validation fails, the reason from the database appears above the editor; a failure with no readable reason reads Query validation failed. A successful validation opens the Query Data Preview window with the query's result.
Validation runs the query for up to 30 minutes. A query that runs longer fails. SQL dialect and data scope covers the SQL you can use.
While the tile says Loading editor, the editor is still starting.
Dependencies is read-only. It lists the upstream tables this table reads, grouped by kind, with a count on each group. The list refreshes when you save General.
If the table reads nothing registered, the step shows No dependencies with the text "This write-back has no upstream tables registered as dependencies."
Open the Preview tab. It shows up to 1,000 rows of the source data, with the mapped columns renamed to the target column names. Use the toolbar to search, show or hide columns, page through the rows and export them.
If the preview cannot load, it shows Preview Error with the reason and a Retry button.
Saving, reverting and unsaved changes are covered in full on Save and revert your changes. If the step cannot be saved, a Validation Error toast tells you what is missing; check the Workflow, the table or the query. See Writeback troubleshooting for the message list.
| To do this | You need |
|---|---|
| Open the editor and see the Preview tab | View WriteBack Objects |
| Click Validate, Apply or Finish | Add/Modify WriteBack Objects |
See Writeback permissions for the full list.
Changing the source rebuilds your column mapping. Each of these rebuilds it from matching column names: saving a different source table, switching between table and query, and changing the query so it no longer returns a column you mapped. Columns you mapped by hand are replaced, and a mapped column whose name is gone is dropped. If no column matches, the table is no longer deployed and does not run. Check Columns after every change to the source.
Use a query when you need to filter, join or reshape data before it is written. Turn Table Selection off, write the query and click Validate.
Only deployed tables are offered. Deploy the Lake table first, using Configure a table.
Apply checks the step before it saves. Choose a Workflow, pick a table or, in query mode, click Validate after your last change.
The mapping is rebuilt from matching column names when you save a different source table, switch between table and query, or change the query so it no longer returns a column you mapped. Check Map columns after each change.
Columns with the same name in the source and the target are matched automatically, ignoring case, when the configuration is saved. Columns with no match stay unmapped.
Yes. Click Open in Editor. The query opens in the Editor, in a new console named after the table. Copy your final version back into the Writeback editor and click Validate.
Validation runs your query for up to 30 minutes. A query that runs longer fails, and the editor shows the error.
The preview shows the source values with the mapped columns renamed to the target names, up to 1,000 rows. When the table runs, each value is converted to the data type of its target column, so a value can look different in the destination.
Yes. On General, choose another Workflow and click Apply. To move several tables at once, see Transfer tables between workflows.
No. Each destination table has a single configuration, so it appears once in the tree and is configured once.