Review test results and finalize a transformation

After a test run finishes, the Test Results drawer shows what the query read from the source and what it would write to the target. Review both sides, then finalize the transformation to complete the process.

To start a test and read its log first, see Run and monitor transformation tests. This page covers the drawer itself: the source and target review, the SQL view and the finalize step.

Review the source rows

  1. On the Validation step, click Show Results after a successful test run. The drawer opens on Source Table.
  2. Check the rows the query read for the test date. The preview shows at most 1,000 rows, so a large output is cut to that size and has no paging.
  3. Click Next: Target Output when you have seen enough.

If the run returned no source rows, the drawer reads "No source results available" and offers View SQL Query, so you can still check the transformation logic.

Review the target output

Check the SQL behind the run

Finalize the transformation

  1. Open Source Table and Target Output once each; Finalize unlocks only after both. Until then its description reads "Review source and target first to unlock." Once unlocked, it reads "Confirm and complete the transformation."
  2. Click Finalize Transformation in the footer, or Finalize in the sidebar.
  3. In the Finalize Transformation dialog, read the message: "Are you sure you want to finalize this transformation? This action will complete the transformation process and cannot be undone." Click Finalize to confirm.
  4. On success, a "Transformation finalized successfully" message confirms, and the drawer shows the Finalized badge with a success banner.
  5. If the request fails, the dialog stays open and shows the reason; when no reason comes back, it reads "Failed to finalize transformation". Fix the cause, then click Finalize again.

After finalizing, Execute Now is available on the Execution tab; see Run a transformation and read the Run Log.

Warning

Finalizing cannot be undone. Check Source Table and Target Output before you confirm.

Close without finalizing

Questions, answered

Why is Finalize locked?

Finalize unlocks only after you open Source Table and Target Output once each. Until then its description reads "Review source and target first to unlock." A step counts as reviewed as soon as you land on it, so open the missing side and Finalize Transformation becomes available.

What do the badges under Data Changes mean?

They count the target output by change type, taken from the DML Type column. One badge appears per type found, such as 12 Insert or 3 Update.

Why can't I see more than 1,000 rows in the test results?

A test run's output is capped at 1,000 rows per side, so the preview shows at most that many and has no paging.

Why is the "... Key" column missing from Target Output?

The target preview hides the auto-generated key column named after the target table, whose name ends in Key. It is created for the table automatically and is not part of your column mapping.

Can I undo a finalize?

No. The confirmation states that finalizing cannot be undone. To change a finalized transformation, open a copy and adjust it; see Build, test and finalize a transformation.

Why did closing the results show "Unfinalized Transformation"?

The transformation has not been finalized yet, so the drawer asks before closing. The test run is not affected: click Close Without Finalizing to close, and finalize later when you are ready.

How do I get back to the results after closing?

Click Show Results on the Validation step again. The drawer starts fresh on Source Table, so open both sides once more to unlock Finalize.

Why are the SQL buttons greyed out?

Both SQL Query and Copy SQL are disabled while the transformation has no query. Add one on the Query step; see Write and validate a transformation query.

What happens after I finalize?

The drawer shows the Finalized badge and a success message, and the transformation is complete. Execute Now becomes available on the Execution tab; see Run a transformation and read the Run Log.

What do the numbers next to the results steps mean?

They count the rows in that step's output. A step you have already opened shows a check instead of the number, and a step whose output has no rows shows no count.