DiscoveryVIP / Apps Script AcademyHelp

3. Exploring the Apps Script editor

Module 1 · 20 minutes · Lesson 2; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use exploring the apps script editor without changing the wrong data?

Predict

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

Understand

Code.gs is a server script file in the real editor. A file can define several functions. The function picker selects an entry point, not a line of code. console.log records diagnostic text without changing a sheet. In this academy the Source editor plays the role of Code.gs, while the function field chooses which function to call. Saving a draft and running it are separate actions.

Example 1: Working automation

Calling the helper produces the second message. A helper definition alone produces no message.

function main() {
  console.log("Code.gs is ready");
  describeProject();
}
function describeProject() {
  console.log("Bound spreadsheet project");
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log("Code.gs is ready");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: describeProject();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function describeProject() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 6: console.log("Bound spreadsheet project");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 7: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Code.gs is ready",
    "Bound spreadsheet project"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 2: Investigate a reproducible failure

Predict the effect of // describeProject(); and identify the first mismatch. This example is intentionally faulty.

function main() {
  console.log("Code.gs is ready");
  // describeProject();
}
function describeProject() {
  console.log("Bound spreadsheet project");
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log("Code.gs is ready");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: // describeProject();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function describeProject() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 6: console.log("Bound spreadsheet project");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 7: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Code.gs is ready"
  ],
  "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() {
  console.log("Code.gs is ready");
  describeProject();
}
function describeProject() {
  console.log("Bound spreadsheet project");
}
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: console.log("Code.gs is ready");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: describeProject();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function describeProject() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 6: console.log("Bound spreadsheet project");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 7: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 8: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 9: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
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: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Code.gs is ready",
    "Bound spreadsheet project",
    "Code.gs is ready",
    "Bound spreadsheet project"
  ],
  "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() {
  console.log("Code.gs is ready");
  describeProject();
}
function describeProject() {
  console.log("Bound spreadsheet project");
}
function main() {
  console.log("Start: Exploring the Apps Script editor");
  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: console.log("Code.gs is ready");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: describeProject();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function describeProject() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 6: console.log("Bound spreadsheet project");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 7: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 8: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 9: console.log("Start: Exploring the Apps Script editor");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 10: try { lessonAction(); console.log("Completed operation"); }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 11: 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 12: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Start: Exploring the Apps Script editor",
    "Code.gs is ready",
    "Bound spreadsheet project",
    "Completed operation"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Build and test

Repair the supplied script so that: Calling the helper produces the second message. A helper definition alone produces no message. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  console.log("Code.gs is ready");
  // describeProject();
}
function describeProject() {
  console.log("Bound spreadsheet project");
}

Graduated hints

Hint 1

Inspect the operation containing // describeProject();. Compare it with the stated rule and the first mismatch.

Hint 2

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

Hint 3

The reference uses describeProject(); where the broken source uses // describeProject();. Explain why before applying it.

Reference solution

function main() {
  console.log("Code.gs is ready");
  describeProject();
}
function describeProject() {
  console.log("Bound spreadsheet project");
}

Explain and reflect

Which operation proves the intended result in exploring the apps script editor? 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. 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: Writing and running your first script