Google Sheets fires one edit event for a whole
pasted or filled-down block, not one event per cell. A naive
onEdit handler that only looks at
e.range.getRow() — the first row of that block — will
silently miss every other row you just pasted. SmartStamp checks
the entire affected range, row by row, in that same event.
What happens on a multi-row paste
- You paste (or fill down) a block of values into a watched column — say, 8 rows at once.
- SmartStamp reads the whole affected range from the edit event, not just its first cell.
- Each row is checked against the rule's condition (if any) independently.
- Every row that qualifies gets stamped in the same pass — rows that don't qualify are left alone.
It's the same rule you'd use for a single edit; nothing extra to configure. A range with a condition (see stamping only when a condition is met) works the same way on a paste: SmartStamp checks every pasted row against your rule and stamps each one that qualifies, not every pasted row unconditionally.
Clamped to your configured range
A watched range has a fixed row span (e.g. rows 2–500). If a paste extends beyond it — say you paste 20 rows starting near the bottom of a 500-row range — SmartStamp clamps the check to the rows that actually overlap the configured range. Rows inside the paste but outside the range are ignored; nothing errors, and rows fully inside the range are unaffected by the overlap.
Already-populated rows aren't touched by a paste
A multi-row paste only reacts to the cells that were actually part of that paste event. Rows that already had data before the paste, and weren't included in it, are unaffected — for those, use backfill instead, which checks a whole range on demand rather than reacting to an edit.
Paste with confidence
Set up a rule once — a single row edit or an 8-row paste get the same treatment, no extra code.
See how it works →