A transfer moves a Writeback table from one workflow of a destination to another workflow of the same destination. Use it to regroup tables when a workflow grows too large, or to run a table on a different schedule: a table runs with the workflow it belongs to.
Transferred <n> table(s). appear. The tables leave the source side and show under the target workflow, marked New for a moment.You do not have permission to modify any destination workflow here.The button under the arrow, with the tooltip Swap source and destination workflows, trades the two sides of the view, so you can move tables in the other direction. A swap needs a chosen destination workflow, and permission to modify the workflow that will receive the tables after the swap. It clears your ticked tables, so tick them again for the new direction.
| To | You need |
|---|---|
| See the Workflows button and the view | View WriteBack Workflow Objects |
| Move tables | Add/Modify WriteBack Objects, and Modify WriteBack Workflows on the workflow you move them into |
Without View WriteBack Workflow Objects, the Workflows button is hidden. Without permission to modify a target workflow, the view does not offer it. See Writeback permissions for the full list.
No other workflows with the same type on this destination. Check the destination's workflows, then try again.Pick a destination from the left panel to start transferring tables between workflows. Before you choose a source workflow, it reads Select a source workflow with Choose the workflow that contains the tables you want to move. Only fully mapped tables can be transferred.The list holds the fully mapped tables of the workflow selected in the left panel. A table that is not mapped stays out: open it, map at least one column on Columns and click Apply. If the table is on another workflow, select that workflow first. See Map columns.
The view offers only workflows of the same type on the same destination, and it never offers replication workflows. If none qualifies, it warns No other workflows with the same type on this destination. Check or create the destination's workflows first. See Run, schedule and monitor Writeback.
It switches on when you have ticked at least one table and a destination workflow is chosen. It is also off while a transfer is running. When you cannot modify any destination workflow, its tooltip reads You do not have permission to modify any destination workflow here. See Writeback permissions.
Only its workflow. The table keeps its destination, its source and its column mapping, and it stays Mapped. From now on it runs with the target workflow and follows that workflow's schedule.
No. A transfer stays inside one destination, and the view offers only that destination's workflows. Each Writeback workflow belongs to one destination.
Transfer the tables back. Select them in the workflow they are on now and move them to the original workflow; the view has no separate undo.
A table needs a primary key column to move. A table without one shows No PK and cannot be ticked, even when it is fully mapped.
It ticks every table the list currently shows. With a search active, only the matches are ticked. When everything shown is ticked, the button reads Clear and unticks them all.
It trades the source and destination sides, so you can move tables in the other direction. A swap needs a chosen destination workflow, and permission to modify the workflow that will receive the tables. It clears your ticked tables.
Under the target workflow in the Workflows view; it is marked New for a moment after it arrives. To check later, open the table and read Workflow on the General step. See Configure a Writeback table.