Overview
When Match groups are approved, Zwiron can produce a golden record for each group using the project’s Survivorship settings. Write back approved on the run results hub upserts those golden rows to a destination table so downstream systems can use a single surviving record. Write-back is started from the run results hub, not from sync Jobs under Data → Jobs.Survivorship
Configure survivorship on the Match project (Edit, create form, or Advanced):
On an approved group, stewards may Edit golden / Save golden before write-back, or Regenerate golden to rebuild from rules.
Destination settings
On the project (Show advanced scoring & write-back or Advanced):Write-back requires a usable destination (connection + table) and at least one approved golden. If write-back fails, verify destination permissions and that groups were approved (goldens exist for the run).
Write back approved goldens
To write back from a run:- Open the run results hub (Match review from Match → Review, or open the run from the project).
- Ensure groups you intend to publish are approved (clear For Review for those groups).
- Click Write back approved.
- Confirm the success message (rows written and groups merged).
- Optionally open Reviewed, or use overflow actions to Export goldens CSV / Export groups CSV.
Write back approved is disabled when there is nothing useful to write (for example all groups still pending and none reviewed). Approve groups first.
Catalog and Trust close-loop
If the Match project is linked to a Catalog table:- Write-back records Know lineage for the movement of golden data
- Trust re-detect may run on that asset so quality and incidents stay current
- Golden rows are still written when write-back succeeds
- The Know / Trust close-loop is skipped (the product reports this in the write-back result note)
Export without write-back
From the run hub overflow menu:
Use exports for audit or offline review before or after write-back.