Rearrange transformations

The Rearrange view moves Warehouse transformations from one workflow to another. Use it when a table's transformations should run in a different Warehouse workflow.

Open the Rearrange view

1. Open the diagram for a run, as described in Workflow diagram.
2. In the SETTINGS PANEL, click Rearrange. The same panel switches to Flow and Summary; see Summary view.
3. The view lists Warehouse transformations in groups, one per table and source system.

The tool works from the transformation list, not from run data, so it is available even when the workflow has no runs yet.

Move groups to another workflow

1. Type in Filter tables, source systems, transformations… to narrow the list. The filter matches table names, source system names and transformation names.
2. Tick the checkbox of each group you want to move. A group's checkbox is named after its table and source system, in the form Select {table} / {sourceSystem}.
3. Choose the destination in Target workflow. The list holds Warehouse workflows only.
4. Click Move N groups (M): N is the number of ticked groups, and M is the number of transformations they hold. With one group ticked, the button reads Move 1 group (M).
5. Wait while the button reads Moving…. The result arrives as a notification.

What the list shows

• One group per table and source system, ordered by table name, then source system.
• A group shows the table name, its source system badge, and its count, N transformation or N transformations.
• Each transformation appears as a chip with its name, a Finalized badge when it is finalized, and an arrow to the workflow it currently belongs to. Unassigned means it is not in a Warehouse workflow yet.
• While the list loads, it shows Loading transformations.

After a move

• The chosen workflow runs the moved transformations from that workflow's next run. A run that is already going keeps the plan it started with.
• Transformations keep their status, so a finalized transformation stays finalized.
• The tick marks clear and the list reloads. A Success notification reads N transformation(s) were moved into "{workflow}" successfully.

Move rules and refusals

• Keep a table's finalized transformations in one workflow. Transformations that write the same table from the same source system must all belong to the same workflow, so move them together in a single move. A move that would leave finalized transformations of the group behind is refused.
• A run in progress blocks a move. If a run of the source or the target workflow is going, the move is refused; wait for it to finish and try again.
• A refusal arrives as an Error notification with the server's explanation below the title. When the server sends no explanation, the notification reads Failed to move transformations.

Who can move transformations

Moving needs Add/Modify Warehouse Objects, from the Data Layer category. Without it, the group checkboxes and the Move button stay disabled, and the server refuses the move as the final check. You also need the permission that opens the diagram for the run. The full picture is in Workflow permissions and Warehouse permissions and row-level security.

Questions, answered

Which workflows can I move transformations into?

Warehouse workflows only. The Target workflow list holds Warehouse workflows, because transformations run in Warehouse workflows alone. Lake and WriteBack workflows never appear.

Why is the Move button greyed out?

One of four reasons: you lack Add/Modify Warehouse Objects, no destination is chosen in Target workflow, no group is ticked, or a move is already in progress and the button reads Moving….

What do the numbers on the Move button mean?

Move N groups (M): N is how many groups you ticked, and M is how many transformations they hold. With one group ticked, the button reads Move 1 group (M).

How are the transformations grouped?

One group per table and source system, ordered by table name, then source system. The count beside a group shows how many transformations it holds.

What does Unassigned mean on a transformation chip?

The transformation is not in a Warehouse workflow yet. Its chip shows Unassigned after the arrow. Tick its group, choose a Target workflow, and move the group to place it in one.

What does the Finalized badge mean?

It marks a finalized transformation, the state a workflow needs to run it. See Build, test and finalize a transformation.

Can I move transformations while a run is going?

No. A move is refused while a run of the source or the target workflow is in progress. Wait for it to finish and try again.

When do the moved transformations start running in the new workflow?

From that workflow's next run. A run that is already going keeps the plan it started with, and every transformation keeps its status, so a finalized one stays finalized.

Why does the list say "No transformations match."?

The filter is hiding every group. It matches table names, source system names and transformation names, so clear it or check the spelling. If the list stays empty without a filter, there are no transformations to move.

Do I need a finished run to use Rearrange?

No. The view works from the transformation list, not from run data, so it is available even before the workflow's first run.