47. Creating forms
Module 10 · 20 minutes · Lesson 46; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use creating forms without changing the wrong data?
- Explain creating forms in your own words
- Trace the actual forms state change 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
Creating a form returns a new Form object. Add questions after creation and configure any destination explicitly. The form ID is required for later access. Creating another form on every scheduled run is usually a mistake; store its ID for reuse. The example generates a single sample form without collecting real data.
Example 1: Working automation
The new form contains a required text question and is separate from the existing Feedback form.
function main() {
const form = FormApp.create("Workshop registration");
form.addTextItem().setTitle("Name").setRequired(true);
console.log(form.getId());
}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.create("Workshop registration");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: form.addTextItem().setTitle("Name").setRequired(true);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 4: console.log(form.getId());
- 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": [
"form-1"
],
"error": null,
"resource": "forms",
"value": {
"feedback": {
"name": "Feedback",
"items": [
"Name",
"Comment"
],
"responses": [
{
"Name": "Alex",
"Comment": "Helpful"
}
]
},
"form-1": {
"name": "Workshop registration",
"items": [
{
"title": "Name",
"type": "text",
"required": true
}
],
"responses": []
}
}
}Example 2: Investigate a reproducible failure
Predict the effect of setRequired(false) and identify the first mismatch. This example is intentionally faulty.
function main() {
const form = FormApp.create("Workshop registration");
form.addTextItem().setTitle("Name").setRequired(false);
console.log(form.getId());
}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.create("Workshop registration");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: form.addTextItem().setTitle("Name").setRequired(false);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 4: console.log(form.getId());
- 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": [
"form-1"
],
"error": null,
"resource": "forms",
"value": {
"feedback": {
"name": "Feedback",
"items": [
"Name",
"Comment"
],
"responses": [
{
"Name": "Alex",
"Comment": "Helpful"
}
]
},
"form-1": {
"name": "Workshop registration",
"items": [
{
"title": "Name",
"type": "text",
"required": false
}
],
"responses": []
}
}
}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.create("Workshop registration");
form.addTextItem().setTitle("Name").setRequired(true);
console.log(form.getId());
}
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.create("Workshop registration");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: form.addTextItem().setTitle("Name").setRequired(true);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 4: console.log(form.getId());
- 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": [
"form-1",
"form-2"
],
"error": null,
"resource": "forms",
"value": {
"feedback": {
"name": "Feedback",
"items": [
"Name",
"Comment"
],
"responses": [
{
"Name": "Alex",
"Comment": "Helpful"
}
]
},
"form-1": {
"name": "Workshop registration",
"items": [
{
"title": "Name",
"type": "text",
"required": true
}
],
"responses": []
},
"form-2": {
"name": "Workshop registration",
"items": [
{
"title": "Name",
"type": "text",
"required": true
}
],
"responses": []
}
}
}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.create("Workshop registration");
form.addTextItem().setTitle("Name").setRequired(true);
console.log(form.getId());
}
function main() {
console.log("Start: Creating forms");
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.create("Workshop registration");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: form.addTextItem().setTitle("Name").setRequired(true);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 4: console.log(form.getId());
- 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: Creating forms");
- 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: Creating forms",
"form-1",
"Completed operation"
],
"error": null,
"resource": "forms",
"value": {
"feedback": {
"name": "Feedback",
"items": [
"Name",
"Comment"
],
"responses": [
{
"Name": "Alex",
"Comment": "Helpful"
}
]
},
"form-1": {
"name": "Workshop registration",
"items": [
{
"title": "Name",
"type": "text",
"required": true
}
],
"responses": []
}
}
}Build and test
Repair the supplied script so that: The new form contains a required text question and is separate from the existing Feedback form. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const form = FormApp.create("Workshop registration");
form.addTextItem().setTitle("Name").setRequired(false);
console.log(form.getId());
}Graduated hints
Hint 1
Inspect the operation containing setRequired(false). Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns setRequired(true). Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses setRequired(true) where the broken source uses setRequired(false). Explain why before applying it.
Reference solution
function main() {
const form = FormApp.create("Workshop registration");
form.addTextItem().setTitle("Name").setRequired(true);
console.log(form.getId());
}Explain and reflect
Which operation proves the intended result in creating forms? Which wrong input would expose a weakness, and what would remain unchanged?
Adapt the input records and forms 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 forms 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.