DiscoveryVIP / Apps Script AcademyHelp

67. Alerts and prompts

Module 14 · 20 minutes · Lesson 66; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use alerts and prompts without changing the wrong data?

Predict

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

Understand

A UI prompt returns an object containing both the selected button and response text. A canceled prompt should not trigger a write. The local adapter supplies a configurable sample response and is not a modal Google UI. Real alert and prompt calls can suspend the server script; do not assume locks remain held across them.

Example 1: Working automation

Calling getResponseText obtains the fictional response, while the uncalled method is not the learner’s text.

function main() {
  const ui = SpreadsheetApp.getUi();
  const response = ui.prompt("What is your name?");
  ui.alert("Hello, " + response.getResponseText());
}
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 ui = SpreadsheetApp.getUi();
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: const response = ui.prompt("What is your name?");
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 4: ui.alert("Hello, " + response.getResponseText());
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": null,
  "resource": "ui",
  "value": {
    "type": "alert",
    "content": "Hello, Alex"
  }
}

Example 2: Investigate a reproducible failure

Predict the effect of response.getResponseText and identify the first mismatch. This example is intentionally faulty.

function main() {
  const ui = SpreadsheetApp.getUi();
  const response = ui.prompt("What is your name?");
  ui.alert("Hello, " + response.getResponseText);
}
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 ui = SpreadsheetApp.getUi();
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: const response = ui.prompt("What is your name?");
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 4: ui.alert("Hello, " + response.getResponseText);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": null,
  "resource": "ui",
  "value": {
    "type": "alert",
    "content": "Hello, ()=>faults.promptText??'Alex'"
  }
}

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 ui = SpreadsheetApp.getUi();
  const response = ui.prompt("What is your name?");
  ui.alert("Hello, " + response.getResponseText());
}
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 ui = SpreadsheetApp.getUi();
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: const response = ui.prompt("What is your name?");
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 4: ui.alert("Hello, " + response.getResponseText());
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
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": [],
  "error": null,
  "resource": "ui",
  "value": {
    "type": "alert",
    "content": "Hello, Alex"
  }
}

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 ui = SpreadsheetApp.getUi();
  const response = ui.prompt("What is your name?");
  ui.alert("Hello, " + response.getResponseText());
}
function main() {
  console.log("Start: Alerts and prompts");
  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 ui = SpreadsheetApp.getUi();
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: const response = ui.prompt("What is your name?");
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 4: ui.alert("Hello, " + response.getResponseText());
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
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: Alerts and prompts");
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: Alerts and prompts",
    "Completed operation"
  ],
  "error": null,
  "resource": "ui",
  "value": {
    "type": "alert",
    "content": "Hello, Alex"
  }
}

Build and test

Repair the supplied script so that: Calling getResponseText obtains the fictional response, while the uncalled method is not the learner’s text. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  const ui = SpreadsheetApp.getUi();
  const response = ui.prompt("What is your name?");
  ui.alert("Hello, " + response.getResponseText);
}

Graduated hints

Hint 1

Inspect the operation containing response.getResponseText. Compare it with the stated rule and the first mismatch.

Hint 2

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

Hint 3

The reference uses response.getResponseText() where the broken source uses response.getResponseText. Explain why before applying it.

Reference solution

function main() {
  const ui = SpreadsheetApp.getUi();
  const response = ui.prompt("What is your name?");
  ui.alert("Hello, " + response.getResponseText());
}

Explain and reflect

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

Adapt the input records and ui 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 ui 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: HTML Service dialogs