DiscoveryVIP / Apps Script AcademyHelp

25. Appending, inserting and removing safely

Module 5 · 20 minutes · Lesson 24; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use appending, inserting and removing safely without changing the wrong data?

Predict

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

Understand

appendRow adds data after the used rows. Deleting rows shifts later coordinates, so delete from the bottom when removing multiple matches. Keep backups and confirm destructive production operations. The academy runs against a resettable copy; undo restores the prior local state. An append is not automatically protected from duplicate execution.

Example 1: Working automation

The new row increases the used row count by one and preserves existing people.

function main() {
  const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  sheet.appendRow(["Sam", "Pending"]);
  console.log(sheet.getLastRow());
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 3: sheet.appendRow(["Sam", "Pending"]);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: console.log(sheet.getLastRow());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "5"
  ],
  "error": null,
  "resource": "sheets",
  "value": {
    "People": [
      [
        "Name",
        "Status"
      ],
      [
        "Alex",
        "Pending"
      ],
      [
        "Jordan",
        "Pending"
      ],
      [
        "Morgan",
        "Pending"
      ],
      [
        "Sam",
        "Pending"
      ]
    ],
    "Sales": [
      [
        "Customer",
        "Amount",
        "Approved"
      ],
      [
        "Alex",
        120,
        true
      ],
      [
        "Jordan",
        80,
        false
      ],
      [
        "Morgan",
        200,
        true
      ]
    ],
    "Tasks": [
      [
        "Task",
        "Status"
      ],
      [
        "Review invoice",
        "Open"
      ],
      [
        "Publish report",
        "Complete"
      ]
    ]
  }
}

Example 2: Investigate a reproducible failure

Predict the effect of // no append and identify the first mismatch. This example is intentionally faulty.

function main() {
  const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  // no append
  console.log(sheet.getLastRow());
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 3: // no append
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: console.log(sheet.getLastRow());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "4"
  ],
  "error": null,
  "resource": "sheets",
  "value": {
    "People": [
      [
        "Name",
        "Status"
      ],
      [
        "Alex",
        "Pending"
      ],
      [
        "Jordan",
        "Pending"
      ],
      [
        "Morgan",
        "Pending"
      ]
    ],
    "Sales": [
      [
        "Customer",
        "Amount",
        "Approved"
      ],
      [
        "Alex",
        120,
        true
      ],
      [
        "Jordan",
        80,
        false
      ],
      [
        "Morgan",
        200,
        true
      ]
    ],
    "Tasks": [
      [
        "Task",
        "Status"
      ],
      [
        "Review invoice",
        "Open"
      ],
      [
        "Publish report",
        "Complete"
      ]
    ]
  }
}

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() {
  const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  sheet.appendRow(["Sam", "Pending"]);
  console.log(sheet.getLastRow());
}
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: const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 3: sheet.appendRow(["Sam", "Pending"]);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: console.log(sheet.getLastRow());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 6: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 7: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 8: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 9: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "5",
    "6"
  ],
  "error": null,
  "resource": "sheets",
  "value": {
    "People": [
      [
        "Name",
        "Status"
      ],
      [
        "Alex",
        "Pending"
      ],
      [
        "Jordan",
        "Pending"
      ],
      [
        "Morgan",
        "Pending"
      ],
      [
        "Sam",
        "Pending"
      ],
      [
        "Sam",
        "Pending"
      ]
    ],
    "Sales": [
      [
        "Customer",
        "Amount",
        "Approved"
      ],
      [
        "Alex",
        120,
        true
      ],
      [
        "Jordan",
        80,
        false
      ],
      [
        "Morgan",
        200,
        true
      ]
    ],
    "Tasks": [
      [
        "Task",
        "Status"
      ],
      [
        "Review invoice",
        "Open"
      ],
      [
        "Publish report",
        "Complete"
      ]
    ]
  }
}

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() {
  const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  sheet.appendRow(["Sam", "Pending"]);
  console.log(sheet.getLastRow());
}
function main() {
  console.log("Start: Appending, inserting and removing safely");
  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: const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 3: sheet.appendRow(["Sam", "Pending"]);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: console.log(sheet.getLastRow());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 6: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 7: console.log("Start: Appending, inserting and removing safely");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 8: try { lessonAction(); console.log("Completed operation"); }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 9: 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 10: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Start: Appending, inserting and removing safely",
    "5",
    "Completed operation"
  ],
  "error": null,
  "resource": "sheets",
  "value": {
    "People": [
      [
        "Name",
        "Status"
      ],
      [
        "Alex",
        "Pending"
      ],
      [
        "Jordan",
        "Pending"
      ],
      [
        "Morgan",
        "Pending"
      ],
      [
        "Sam",
        "Pending"
      ]
    ],
    "Sales": [
      [
        "Customer",
        "Amount",
        "Approved"
      ],
      [
        "Alex",
        120,
        true
      ],
      [
        "Jordan",
        80,
        false
      ],
      [
        "Morgan",
        200,
        true
      ]
    ],
    "Tasks": [
      [
        "Task",
        "Status"
      ],
      [
        "Review invoice",
        "Open"
      ],
      [
        "Publish report",
        "Complete"
      ]
    ]
  }
}

Build and test

Repair the supplied script so that: The new row increases the used row count by one and preserves existing people. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  // no append
  console.log(sheet.getLastRow());
}

Graduated hints

Hint 1

Inspect the operation containing // no append. Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns sheet.appendRow(["Sam", "Pending"]);. Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses sheet.appendRow(["Sam", "Pending"]); where the broken source uses // no append. Explain why before applying it.

Reference solution

function main() {
  const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  sheet.appendRow(["Sam", "Pending"]);
  console.log(sheet.getLastRow());
}

Explain and reflect

Which operation proves the intended result in appending, inserting and removing safely? Which wrong input would expose a weakness, and what would remain unchanged?

Adapt the input records and sheets output 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 sheets 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. Use Manual unless investigating a trigger. 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: Formatting ranges