Contact

Zoho Sheet · Data cleanup · Beginner

Review and Remove Duplicate Records in Zoho Sheet

Review duplicate keys, preserve legitimate order lines and reconcile safe whole-row removals.

Editorial standards

Quick answer

Use Data → Data Cleaning → Find Duplicates to review a business key, not to guess which complete record will survive. Preserve the baseline, highlight candidates and remove only verified whole rows in the disposable working copy.

A repeated order number is not necessarily a duplicate order line. Review explicit keys before removing records, and keep the original row IDs so the result can be reconciled.

Preserve a full source

On a sheet named Records, enter A1 Import ID, B1 Order, C1 Line, D1 Item and E1 Units, then enter:

Row A: Import ID B: Order C: Line D: Item E: Units
2 I01 O10 1 Pen 2
3 I02 O10 2 Pad 1
4 I03 O10 1 Pen 2
5 I04 O11 1 Pen 3
6 I05 O12 1 Folder 4
7 I06 O12 1 Folder 4

There are six imported rows and 16 units. In G1 enter Line key; in G2 enter =B2&"/"&C2 and fill through G7. Keys are O10/1, O10/2, O10/1, O11/1, O12/1, O12/1. There are four distinct business lines. For this synthetic exercise the policy is to retain the lowest import ID for an otherwise identical order-line record: I01, I02, I04, I05, totaling 10 units.

Use File → Save As to preserve Duplicate Records Baseline, record its cloud URL, then make Duplicate Records Working. Never experiment on the only original.

Use Data Cleaning for review

  1. Activate Records in Working. Select G2:G7, excluding the heading.
  2. Choose Data → Data Cleaning → Find Duplicates. Read the duplicate/unique counts before selecting an action.
  3. Review the repeated keys O10/1 and O12/1 against columns A:E. There are two duplicate groups, four members in those groups, and two excess records. A UI count may mean members or excess copies; identify what it counts before comparing numbers.
  4. Prefer the documented highlight action for this first pass. Check that only keys for rows 2,4,6,7 are implicated. Highlighting does not itself delete any record.
  5. Check full content: I01 and I03 differ in import ID, but B:E match. Including Import ID in a full-row comparison would make all six rows unique. Conversely, using Order alone would wrongly collapse the legitimate second line I02 for O10.

The public web help documents delete, highlight, move and copy actions, but does not specify complete-row deletion, comparison-column selection or which occurrence is retained. Do not infer those controls from Excel. In particular, deleting duplicates from G alone is not evidence that corresponding A:E records were removed safely.

Remove only the reviewed records

For the reproducible safe path, use the reviewed IDs to delete complete worksheet rows on this disposable working copy. First verify I06 is still row 7, select its row header, and choose Delete Row from the context menu. Then verify I03 is still row 4 and delete that row. Deleting bottom-up avoids shifting the earlier target. Check the ID in each row before deletion; never delete a row just because its old row number is written here.

The remaining A2:A5 must be I01, I02, I04, I05, with E values 2,1,3,4 and total 10. All five fields must remain aligned. This is Data Cleaning-assisted review followed by explicit whole-row removal, not a claim that the undocumented deletion options implement a particular key policy.

Test growth and the wrong key without sacrificing the result

Append I07/O13/1/Pad/5 at row 6 and enter G6 =B6&"/"&C6. Recheck G2:G6 with Find Duplicates. The five keys should be distinct and the total becomes 15. Save as Duplicate Records Complete, record its URL and reopen Records to verify those five IDs and 15 units.

For optional wrong-key practice, open the original baseline and use Save As to make Duplicate Wrong Key Experiment. Review B2:B7 alone: O10 repeats across two legitimate lines. Do not delete. Cancel and restore the intended G2:G7 review range. If you deliberately test deletion options, do so only in this disposable file and only after the pane makes retention and whole-row effects explicit. Recover by making a fresh working copy of the baseline, not by assuming Undo survives reopening.

Blanks, case, whitespace and conflicting values under the same key need separate policies. If repeated keys have different quantities or item names, stop and resolve the conflict; this fixture’s survivor rule is not permission to discard real disagreements.

Scope and verification

Zoho Sheet web editor, English interface, rolling service; cached official documentation retrieved 2026-10-19 and reviewed 2026-10-20. Requires edit access to a private practice spreadsheet. Native browser execution and screenshots are not verified; desktop/offline and mobile parity are outside scope.

The fixture values and state transitions were independently checked outside Zoho Sheet. No account was opened, no native run was performed and no application screenshot is claimed. If your controls differ, stop and consult the current help rather than applying another platform’s instructions.

Official documentation