DiscoveryVIP / Apps Script AcademyHelp

32. Creating and opening documents

Module 7 · 20 minutes · Lesson 31; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use creating and opening documents without changing the wrong data?

Predict

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

Understand

create makes a new document and returns a Document. openById retrieves an existing one by identifier. Store IDs instead of relying on potentially duplicated names. New documents are persistent side effects in Google, so test in a sample folder and consider rerun behavior. The local ID counter is fictional and never opens a real file.

Example 1: Working automation

The created document contains a visible paragraph and receives a locally unique identifier.

function main() {
  const doc = DocumentApp.create("Workshop notes");
  doc.getTabs()[0].asDocumentTab().getBody().appendParagraph("First meeting");
  console.log(doc.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 doc = DocumentApp.create("Workshop notes");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: doc.getTabs()[0].asDocumentTab().getBody().appendParagraph("First meeting");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: console.log(doc.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": [
    "doc-1"
  ],
  "error": null,
  "resource": "docs",
  "value": {
    "template": {
      "name": "Letter template",
      "paragraphs": [
        "Dear {{NAME}},",
        "Your project {{PROJECT}} is scheduled for completion on {{DATE}}."
      ]
    },
    "doc-1": {
      "name": "Workshop notes",
      "paragraphs": [
        "First meeting"
      ]
    }
  }
}

Example 2: Investigate a reproducible failure

Predict the effect of appendParagraph("Wrong meeting") and identify the first mismatch. This example is intentionally faulty.

function main() {
  const doc = DocumentApp.create("Workshop notes");
  doc.getTabs()[0].asDocumentTab().getBody().appendParagraph("Wrong meeting");
  console.log(doc.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 doc = DocumentApp.create("Workshop notes");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: doc.getTabs()[0].asDocumentTab().getBody().appendParagraph("Wrong meeting");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: console.log(doc.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": [
    "doc-1"
  ],
  "error": null,
  "resource": "docs",
  "value": {
    "template": {
      "name": "Letter template",
      "paragraphs": [
        "Dear {{NAME}},",
        "Your project {{PROJECT}} is scheduled for completion on {{DATE}}."
      ]
    },
    "doc-1": {
      "name": "Workshop notes",
      "paragraphs": [
        "Wrong meeting"
      ]
    }
  }
}

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("Workshop notes");
  doc.getTabs()[0].asDocumentTab().getBody().appendParagraph("First meeting");
  console.log(doc.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 doc = DocumentApp.create("Workshop notes");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: doc.getTabs()[0].asDocumentTab().getBody().appendParagraph("First meeting");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: console.log(doc.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": [
    "doc-1",
    "doc-2"
  ],
  "error": null,
  "resource": "docs",
  "value": {
    "template": {
      "name": "Letter template",
      "paragraphs": [
        "Dear {{NAME}},",
        "Your project {{PROJECT}} is scheduled for completion on {{DATE}}."
      ]
    },
    "doc-1": {
      "name": "Workshop notes",
      "paragraphs": [
        "First meeting"
      ]
    },
    "doc-2": {
      "name": "Workshop notes",
      "paragraphs": [
        "First meeting"
      ]
    }
  }
}

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("Workshop notes");
  doc.getTabs()[0].asDocumentTab().getBody().appendParagraph("First meeting");
  console.log(doc.getId());
}
function main() {
  console.log("Start: Creating and opening documents");
  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("Workshop notes");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: doc.getTabs()[0].asDocumentTab().getBody().appendParagraph("First meeting");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: console.log(doc.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 and opening documents");
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 and opening documents",
    "doc-1",
    "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": "Workshop notes",
      "paragraphs": [
        "First meeting"
      ]
    }
  }
}

Build and test

Repair the supplied script so that: The created document contains a visible paragraph and receives a locally unique identifier. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  const doc = DocumentApp.create("Workshop notes");
  doc.getTabs()[0].asDocumentTab().getBody().appendParagraph("Wrong meeting");
  console.log(doc.getId());
}

Graduated hints

Hint 1

Inspect the operation containing appendParagraph("Wrong meeting"). Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns appendParagraph("First meeting"). Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses appendParagraph("First meeting") where the broken source uses appendParagraph("Wrong meeting"). Explain why before applying it.

Reference solution

function main() {
  const doc = DocumentApp.create("Workshop notes");
  doc.getTabs()[0].asDocumentTab().getBody().appendParagraph("First meeting");
  console.log(doc.getId());
}

Explain and reflect

Which operation proves the intended result in creating and opening documents? 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.

Transfer to Google and authorization guide

Next lesson: Paragraphs, headings, lists and tables