Merge Requests
Two records that are one, waiting for a data steward. Approving re-points every reference to the record that stays, in one step, and keeps the other (inactive) so the merge can be undone.
Where to find it
- Module: Platform
- Group: Data & Documents
- Section: Data Quality
- Screen: Merge Requests
Address in the console: /mdm/merge-requests
Read-only list · 7 columns · 4 actions
This list is read-only: its records are written by the work that produces them. A correction, where one is possible at all, is made where the record was created.
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Request | Code | request_no |
| Master | Status | entity |
| Stays | Text | survivor_label |
| Merged into it | Text | merged_label |
| Proposed | Date and time | requested_at |
| Note | Text | decision_note |
| Status | Status | status |
What you can do here
What would move
Approve and merge primary
Asks for confirmation: Re-point every reference to the record that stays? It can be undone.
Asks for: Note
Reject
Asks for: Why not*
Undo merge
Asks for confirmation: Point the moved references back at the merged record and make it active again?
* required
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.