46. Forms, questions and responses
Module 10 · 20 minutes · Lesson 45; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use forms, questions and responses without changing the wrong data?
- Explain forms, questions and responses in your own words
- Trace the actual console result from the source
- Repair the supplied failing operation and verify the result
Predict
Which values or resources will change, and which should stay unchanged? Write your prediction before execution.
Understand
A form’s structure and its submitted responses are separate objects. FormApp reads responses as FormResponse objects with ItemResponse entries. Do not confuse the form’s own submission event with a linked spreadsheet submission event. The local preview contains fictional responses and makes no request to a Google form.
Example 1: Working automation
The known form has one submitted response; a missing ID is an explicit adapter error.
function main() {
const form = FormApp.openById("feedback");
console.log(form.getTitle());
console.log(form.getResponses().length);
}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 form = FormApp.openById("feedback");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: console.log(form.getTitle());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: console.log(form.getResponses().length);
- 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": [
"Feedback",
"1"
],
"error": null,
"resource": "logs",
"value": null
}Example 2: Investigate a reproducible failure
Predict the effect of openById("missing") and identify the first mismatch. This example is intentionally faulty.
function main() {
const form = FormApp.openById("missing");
console.log(form.getTitle());
console.log(form.getResponses().length);
}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 form = FormApp.openById("missing");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: console.log(form.getTitle());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: console.log(form.getResponses().length);
- 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": [],
"error": "Form not found: missing",
"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 form = FormApp.openById("feedback");
console.log(form.getTitle());
console.log(form.getResponses().length);
}
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 form = FormApp.openById("feedback");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: console.log(form.getTitle());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: console.log(form.getResponses().length);
- 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": [
"Feedback",
"1",
"Feedback",
"1"
],
"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 form = FormApp.openById("feedback");
console.log(form.getTitle());
console.log(form.getResponses().length);
}
function main() {
console.log("Start: Forms, questions and responses");
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 form = FormApp.openById("feedback");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: console.log(form.getTitle());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: console.log(form.getResponses().length);
- 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: Forms, questions and responses");
- 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: Forms, questions and responses",
"Feedback",
"1",
"Completed operation"
],
"error": null,
"resource": "logs",
"value": null
}Build and test
Repair the supplied script so that: The known form has one submitted response; a missing ID is an explicit adapter error. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const form = FormApp.openById("missing");
console.log(form.getTitle());
console.log(form.getResponses().length);
}Graduated hints
Hint 1
Inspect the operation containing openById("missing"). Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns openById("feedback"). Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses openById("feedback") where the broken source uses openById("missing"). Explain why before applying it.
Reference solution
function main() {
const form = FormApp.openById("feedback");
console.log(form.getTitle());
console.log(form.getResponses().length);
}Explain and reflect
Which operation proves the intended result in forms, questions and responses? 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.