DiscoveryVIP / Apps Script AcademyHelp

62. onOpen and onEdit

Module 13 · 20 minutes · Lesson 61; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use onopen and onedit without changing the wrong data?

Predict

Which values or resources will change, and which should stay unchanged? Write your prediction before execution.

Understand

Simple triggers run with restrictions and are not a general replacement for authorized installable triggers. A manual click on Run does not supply an event object automatically. Here the event selector prepares e explicitly. Use e.range to identify the edited cell and handle missing e with a clear guard. Avoid assuming every cell edit has a scalar e.value.

Example 1: Working automation

The prepared edit event identifies row two. Selecting Manual deliberately tests the missing-event guard.

function main() {
  onEdit(e);
}
function onEdit(event) {
  if (!event || !event.range) throw new Error("Choose an onEdit event");
  console.log(event.range.getRow());
  console.log(event.value);
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: onEdit(e);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 3: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 4: function onEdit(event) {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 5: if (!event || !event.range) throw new Error("Choose an onEdit event");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 6: console.log(event.range.getRow());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 7: console.log(event.value);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 8: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "2",
    "Complete"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 2: Investigate a reproducible failure

Predict the effect of event.range.getColumn() and identify the first mismatch. This example is intentionally faulty.

function main() {
  onEdit(e);
}
function onEdit(event) {
  if (!event || !event.range) throw new Error("Choose an onEdit event");
  console.log(event.range.getColumn());
  console.log(event.value);
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: onEdit(e);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 3: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 4: function onEdit(event) {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 5: if (!event || !event.range) throw new Error("Choose an onEdit event");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 6: console.log(event.range.getColumn());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 7: console.log(event.value);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 8: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "1",
    "Complete"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 3: Separate setup from execution and inspect repeat behavior

Call the same named operation twice. Compare outputs and resource counts to learn whether this operation is idempotent. Repeated creation is deliberately visible; real exports require a rerun policy.

function lessonAction() {
  onEdit(e);
}
function onEdit(event) {
  if (!event || !event.range) throw new Error("Choose an onEdit event");
  console.log(event.range.getRow());
  console.log(event.value);
}
function main() {
  lessonAction();
  lessonAction();
}
Important line explanations
Line 1: function lessonAction() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: onEdit(e);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 3: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 4: function onEdit(event) {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 5: if (!event || !event.range) throw new Error("Choose an onEdit event");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 6: console.log(event.range.getRow());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 7: console.log(event.value);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 8: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 9: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 10: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 11: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 12: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "2",
    "Complete",
    "2",
    "Complete"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 4: Add a diagnostic boundary around the operation

Observe start, successful completion or a rethrown failure. This optional professional pattern adds error context without swallowing the error or rolling back changes.

function lessonAction() {
  onEdit(e);
}
function onEdit(event) {
  if (!event || !event.range) throw new Error("Choose an onEdit event");
  console.log(event.range.getRow());
  console.log(event.value);
}
function main() {
  console.log("Start: onOpen and onEdit");
  try { lessonAction(); console.log("Completed operation"); }
  catch(error) { console.error("Failed operation: " + error.message); throw error; }
}
Important line explanations
Line 1: function lessonAction() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: onEdit(e);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 3: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 4: function onEdit(event) {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 5: if (!event || !event.range) throw new Error("Choose an onEdit event");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 6: console.log(event.range.getRow());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 7: console.log(event.value);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 8: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 9: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 10: console.log("Start: onOpen and onEdit");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 11: try { lessonAction(); console.log("Completed operation"); }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 12: catch(error) { console.error("Failed operation: " + error.message); throw error; }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 13: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Start: onOpen and onEdit",
    "2",
    "Complete",
    "Completed operation"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Build and test

Repair the supplied script so that: The prepared edit event identifies row two. Selecting Manual deliberately tests the missing-event guard. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  onEdit(e);
}
function onEdit(event) {
  if (!event || !event.range) throw new Error("Choose an onEdit event");
  console.log(event.range.getColumn());
  console.log(event.value);
}

Graduated hints

Hint 1

Inspect the operation containing event.range.getColumn(). Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns event.range.getRow(). Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses event.range.getRow() where the broken source uses event.range.getColumn(). Explain why before applying it.

Reference solution

function main() {
  onEdit(e);
}
function onEdit(event) {
  if (!event || !event.range) throw new Error("Choose an onEdit event");
  console.log(event.range.getRow());
  console.log(event.value);
}

Explain and reflect

Which operation proves the intended result in onopen and onedit? Which wrong input would expose a weakness, and what would remain unchanged?

Adapt the calculation or validation to a second realistic case. Write its expected result before running. Demonstrate one invalid case and explain whether the side effects should be rolled back or retried.

Troubleshooting

If the console is empty, inspect the logs preview: this script may work through state changes. If the function is missing, select main. For a service error inspect the first failed timeline entry and its arguments. Select the prepared event shown in this lesson; Manual has no event object. Changing input data also changes the expected result; restore sample data before the authored checks.

Knowledge check

Explain the key method or operator. Give an exact output for a second input, plus one invalid case. Verify the result in the interactive lesson; written explanations need self or educator review.

Optional AI practice

Explain this concept using the source above. Help implement one small extension and define its tests. Review/debug the source using its actual expected output; cite real method references and never claim execution.

Transfer to Google and authorization guide

Next lesson: Installable triggers