Merge folds a row you created, or a row that has gone Out of Sync, into the Synced row the source now maintains. Your planning data moves onto the real record, the duplicate is removed, and the source keeps refreshing the row from then on.
What you can use it for
- A planned seat becomes a real hire. You added a row months ago with a salary assumption, planned start date, and notes. The new employee now arrives from the source as a Synced row, and you want your assumptions on that row.
- Someone leaves and comes back. Their row dropped out of the source and went Out of Sync, keeping your planning data. On their return the source sends them as a new Synced row.
- Cleaning up duplicates before a forecast cycle so headcount and cost formulas count each person once.
Before you start
- Merge is available in edit mode only, so you need edit access on the table.
- Merge is the one action where your own planning data can be overwritten in a single step, so the drawer shows the result before you commit.
How to merge a row
1. Open the connected table, select the scenario, and select Edit.
2. Select the row to merge: a Manually added or Out of Sync row.
3. Select Merge in the toolbar.
4. In the Merge rows drawer, find the Synced row to merge into. Search by any column using the dropdown and search box above the list.
5. Check the Synced row. The drawer shows it under Synced row and the result under New values.
6. Review the new values, then select Confirm.
7. Select Save on the table.
How the merge works
| Merged row (Manually added or Out of Sync) | Target row (Synced) | |
|---|---|---|
| Custom columns | Moved onto the target | Replaced by the merged row's values, including blanks |
| Source columns | Discarded | Unchanged, and still refreshed by Import |
| Calculated columns | Discarded | Recalculate after the merge |
| Row | Removed from the scenario you are in | Stays, as Synced |
Your values always win, including blanks. If the merged row has an empty assumption and the target has a value, the target's value is replaced with blank. Check the New values preview before you confirm.
Working with scenarios
Merge acts on the scenario you are viewing. If a Manually added row was carried into other scenarios with Copy to Scenario, those copies are untouched; merge them separately in each scenario if you want the same result there.
Examples
A planned hire starts
In January the team adds a row for Engineer 1 with Employee Number TBD, a planned start of 1 December, and a note "Backfill for R. Chen". The hire starts and appears after the next Import as a Synced row with the real start date and salary. In edit mode the analyst selects the Engineer 1 row, selects Merge, searches for the new employee by name, checks her row, and reviews the New values: the note moves across, the Planned Start column moves across, and nothing else changes because the source columns are not part of the merge. She selects Confirm, then Save. One row remains, Synced, with the note on it.
A rehire with planning data
An employee left in March and her row went Out of Sync, still carrying a 4% merit assumption the team had entered. She is rehired in September and the source sends her as a new Synced row. The analyst merges the Out of Sync row into the new one. The merit assumption moves across, and the Out of Sync row is removed from the FY26 Plan scenario.
The blank that overwrites
A manual row has nothing in the Bonus % column; the matching Synced row already has 10%. The New values preview shows Bonus % as blank because the blank will replace the 10%. The analyst selects Cancel, types 10% into the manual row first, then merges.
Other things to know
- Nothing is saved until you select Save on the table. Cancel on the table discards the merge and restores both rows.
- A Synced row cannot be the merged row, and a Manually added or Out of Sync row cannot be the target.
- Delete is separate. If you do not need the planning data, you can delete the Manually added or Out of Sync row instead of merging it.