33. Paragraphs, headings, lists and tables
Module 7 · 20 minutes · Lesson 32; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use paragraphs, headings, lists and tables without changing the wrong data?
- Explain paragraphs, headings, lists and tables in your own words
- Trace the actual docs 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
Document structure supports semantic headings, list items and tables. A heading style helps navigation more than merely bold text. A table input is an array of rows with text cells. Keep content separate from layout decisions and inspect the resulting document structure before generating many files. The simulated preview is a structural representation, not Google’s layout engine.
Example 1: Working automation
The body has a heading, a list item and a two-row table with a distinct owner/task relationship.
function main() {
const doc = DocumentApp.create("Meeting report");
const body = doc.getTabs()[0].asDocumentTab().getBody();
body.appendParagraph("Agenda").setHeading(DocumentApp.ParagraphHeading.HEADING1);
body.appendListItem("Review budget");
body.appendTable([["Owner", "Task"], ["Alex", "Review"]]);
}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 doc = DocumentApp.create("Meeting report");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const body = doc.getTabs()[0].asDocumentTab().getBody();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 4: body.appendParagraph("Agenda").setHeading(DocumentApp.ParagraphHeading.HEADING1);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 5: body.appendListItem("Review budget");
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 6: body.appendTable([["Owner", "Task"], ["Alex", "Review"]]);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 7: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "docs",
"value": {
"template": {
"name": "Letter template",
"paragraphs": [
"Dear {{NAME}},",
"Your project {{PROJECT}} is scheduled for completion on {{DATE}}."
]
},
"doc-1": {
"name": "Meeting report",
"paragraphs": [
"Agenda",
"\u2022 Review budget"
],
"tables": [
[
[
"Owner",
"Task"
],
[
"Alex",
"Review"
]
]
]
}
}
}Example 2: Investigate a reproducible failure
Predict the effect of ["Alex", "Skip"] and identify the first mismatch. This example is intentionally faulty.
function main() {
const doc = DocumentApp.create("Meeting report");
const body = doc.getTabs()[0].asDocumentTab().getBody();
body.appendParagraph("Agenda").setHeading(DocumentApp.ParagraphHeading.HEADING1);
body.appendListItem("Review budget");
body.appendTable([["Owner", "Task"], ["Alex", "Skip"]]);
}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 doc = DocumentApp.create("Meeting report");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const body = doc.getTabs()[0].asDocumentTab().getBody();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 4: body.appendParagraph("Agenda").setHeading(DocumentApp.ParagraphHeading.HEADING1);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 5: body.appendListItem("Review budget");
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 6: body.appendTable([["Owner", "Task"], ["Alex", "Skip"]]);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 7: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "docs",
"value": {
"template": {
"name": "Letter template",
"paragraphs": [
"Dear {{NAME}},",
"Your project {{PROJECT}} is scheduled for completion on {{DATE}}."
]
},
"doc-1": {
"name": "Meeting report",
"paragraphs": [
"Agenda",
"\u2022 Review budget"
],
"tables": [
[
[
"Owner",
"Task"
],
[
"Alex",
"Skip"
]
]
]
}
}
}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 doc = DocumentApp.create("Meeting report");
const body = doc.getTabs()[0].asDocumentTab().getBody();
body.appendParagraph("Agenda").setHeading(DocumentApp.ParagraphHeading.HEADING1);
body.appendListItem("Review budget");
body.appendTable([["Owner", "Task"], ["Alex", "Review"]]);
}
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 doc = DocumentApp.create("Meeting report");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const body = doc.getTabs()[0].asDocumentTab().getBody();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 4: body.appendParagraph("Agenda").setHeading(DocumentApp.ParagraphHeading.HEADING1);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 5: body.appendListItem("Review budget");
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 6: body.appendTable([["Owner", "Task"], ["Alex", "Review"]]);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- 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": [],
"error": null,
"resource": "docs",
"value": {
"template": {
"name": "Letter template",
"paragraphs": [
"Dear {{NAME}},",
"Your project {{PROJECT}} is scheduled for completion on {{DATE}}."
]
},
"doc-1": {
"name": "Meeting report",
"paragraphs": [
"Agenda",
"\u2022 Review budget"
],
"tables": [
[
[
"Owner",
"Task"
],
[
"Alex",
"Review"
]
]
]
},
"doc-2": {
"name": "Meeting report",
"paragraphs": [
"Agenda",
"\u2022 Review budget"
],
"tables": [
[
[
"Owner",
"Task"
],
[
"Alex",
"Review"
]
]
]
}
}
}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 doc = DocumentApp.create("Meeting report");
const body = doc.getTabs()[0].asDocumentTab().getBody();
body.appendParagraph("Agenda").setHeading(DocumentApp.ParagraphHeading.HEADING1);
body.appendListItem("Review budget");
body.appendTable([["Owner", "Task"], ["Alex", "Review"]]);
}
function main() {
console.log("Start: Paragraphs, headings, lists and tables");
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 doc = DocumentApp.create("Meeting report");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const body = doc.getTabs()[0].asDocumentTab().getBody();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 4: body.appendParagraph("Agenda").setHeading(DocumentApp.ParagraphHeading.HEADING1);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 5: body.appendListItem("Review budget");
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 6: body.appendTable([["Owner", "Task"], ["Alex", "Review"]]);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- 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: Paragraphs, headings, lists and tables");
- 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: Paragraphs, headings, lists and tables",
"Completed operation"
],
"error": null,
"resource": "docs",
"value": {
"template": {
"name": "Letter template",
"paragraphs": [
"Dear {{NAME}},",
"Your project {{PROJECT}} is scheduled for completion on {{DATE}}."
]
},
"doc-1": {
"name": "Meeting report",
"paragraphs": [
"Agenda",
"\u2022 Review budget"
],
"tables": [
[
[
"Owner",
"Task"
],
[
"Alex",
"Review"
]
]
]
}
}
}Build and test
Repair the supplied script so that: The body has a heading, a list item and a two-row table with a distinct owner/task relationship. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const doc = DocumentApp.create("Meeting report");
const body = doc.getTabs()[0].asDocumentTab().getBody();
body.appendParagraph("Agenda").setHeading(DocumentApp.ParagraphHeading.HEADING1);
body.appendListItem("Review budget");
body.appendTable([["Owner", "Task"], ["Alex", "Skip"]]);
}Graduated hints
Hint 1
Inspect the operation containing ["Alex", "Skip"]. Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns ["Alex", "Review"]. Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses ["Alex", "Review"] where the broken source uses ["Alex", "Skip"]. Explain why before applying it.
Reference solution
function main() {
const doc = DocumentApp.create("Meeting report");
const body = doc.getTabs()[0].asDocumentTab().getBody();
body.appendParagraph("Agenda").setHeading(DocumentApp.ParagraphHeading.HEADING1);
body.appendListItem("Review budget");
body.appendTable([["Owner", "Task"], ["Alex", "Review"]]);
}Explain and reflect
Which operation proves the intended result in paragraphs, headings, lists and tables? Which wrong input would expose a weakness, and what would remain unchanged?
Adapt the input records and docs 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 docs 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.