DiscoveryVIP / Apps Script AcademyHelp

6. Variables, let and const

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

Open Interactive Lesson

Discover

How can you use variables, let and const without changing the wrong data?

Predict

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

Understand

A binding associates a name with a value. let permits reassignment; const requires an initial value and prevents assigning a different value to that binding. Both have block scope. A descriptive name explains the role of a number better than a short letter. Distinguish assignment (=) from comparison (===). Reassigning a const raises an error even when the new value has the same type.

Example 1: Working automation

The count is incremented before the output is constructed; the customer binding is never reassigned.

function main() {
  const customer = "Alex";
  let count = 1;
  count = count + 1;
  console.log(customer + ": " + count);
}
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 customer = "Alex";
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: let count = 1;
Initialize a local value that can be updated as the calculation or loop proceeds.
Line 4: count = count + 1;
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 5: console.log(customer + ": " + count);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 6: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Alex: 2"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 2: Investigate a reproducible failure

Predict the effect of const count and identify the first mismatch. This example is intentionally faulty.

function main() {
  const customer = "Alex";
  const count = 1;
  count = count + 1;
  console.log(customer + ": " + count);
}
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 customer = "Alex";
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: const count = 1;
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 4: count = count + 1;
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 5: console.log(customer + ": " + count);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 6: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": "Assignment to constant variable.",
  "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() {
  const customer = "Alex";
  let count = 1;
  count = count + 1;
  console.log(customer + ": " + count);
}
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 customer = "Alex";
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: let count = 1;
Initialize a local value that can be updated as the calculation or loop proceeds.
Line 4: count = count + 1;
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 5: console.log(customer + ": " + count);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 6: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 7: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
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: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 10: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Alex: 2",
    "Alex: 2"
  ],
  "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() {
  const customer = "Alex";
  let count = 1;
  count = count + 1;
  console.log(customer + ": " + count);
}
function main() {
  console.log("Start: Variables, let and const");
  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 customer = "Alex";
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: let count = 1;
Initialize a local value that can be updated as the calculation or loop proceeds.
Line 4: count = count + 1;
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 5: console.log(customer + ": " + count);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 6: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 7: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 8: console.log("Start: Variables, let and const");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 9: try { lessonAction(); console.log("Completed operation"); }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 10: 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 11: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Start: Variables, let and const",
    "Alex: 2",
    "Completed operation"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Build and test

Repair the supplied script so that: The count is incremented before the output is constructed; the customer binding is never reassigned. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  const customer = "Alex";
  const count = 1;
  count = count + 1;
  console.log(customer + ": " + count);
}

Graduated hints

Hint 1

Inspect the operation containing const count. Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns let count. Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses let count where the broken source uses const count. Explain why before applying it.

Reference solution

function main() {
  const customer = "Alex";
  let count = 1;
  count = count + 1;
  console.log(customer + ": " + count);
}

Explain and reflect

Which operation proves the intended result in variables, let and const? 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: Strings, numbers and Boolean values