DiscoveryVIP / Apps Script AcademyHelp

57. Creating presentations and slides

Module 12 · 20 minutes · Lesson 56; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use creating presentations and slides without changing the wrong data?

Predict

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

Understand

appendSlide adds a slide and returns it so you can populate it immediately. Keep a consistent layout and decide what to do with the default first slide. A loop that appends without recording the presentation ID can create many duplicate decks on rerun. This example intentionally produces two slides with different roles.

Example 1: Working automation

The default slide introduces Discover and the appended blank slide introduces Experiment.

function main() {
  const deck = SlidesApp.create("Two-part lesson");
  deck.getSlides()[0].insertTextBox("Discover");
  deck.appendSlide(SlidesApp.PredefinedLayout.BLANK).insertTextBox("Experiment");
}
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 deck = SlidesApp.create("Two-part lesson");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: deck.getSlides()[0].insertTextBox("Discover");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: deck.appendSlide(SlidesApp.PredefinedLayout.BLANK).insertTextBox("Experiment");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": null,
  "resource": "presentations",
  "value": {
    "slides-1": {
      "name": "Two-part lesson",
      "slides": [
        {
          "elements": [
            {
              "text": "Discover",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        },
        {
          "elements": [
            {
              "text": "Experiment",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        }
      ]
    }
  }
}

Example 2: Investigate a reproducible failure

Predict the effect of "Wrong section" and identify the first mismatch. This example is intentionally faulty.

function main() {
  const deck = SlidesApp.create("Two-part lesson");
  deck.getSlides()[0].insertTextBox("Discover");
  deck.appendSlide(SlidesApp.PredefinedLayout.BLANK).insertTextBox("Wrong section");
}
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 deck = SlidesApp.create("Two-part lesson");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: deck.getSlides()[0].insertTextBox("Discover");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: deck.appendSlide(SlidesApp.PredefinedLayout.BLANK).insertTextBox("Wrong section");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": null,
  "resource": "presentations",
  "value": {
    "slides-1": {
      "name": "Two-part lesson",
      "slides": [
        {
          "elements": [
            {
              "text": "Discover",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        },
        {
          "elements": [
            {
              "text": "Wrong section",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        }
      ]
    }
  }
}

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 deck = SlidesApp.create("Two-part lesson");
  deck.getSlides()[0].insertTextBox("Discover");
  deck.appendSlide(SlidesApp.PredefinedLayout.BLANK).insertTextBox("Experiment");
}
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 deck = SlidesApp.create("Two-part lesson");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: deck.getSlides()[0].insertTextBox("Discover");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: deck.appendSlide(SlidesApp.PredefinedLayout.BLANK).insertTextBox("Experiment");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
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": "presentations",
  "value": {
    "slides-1": {
      "name": "Two-part lesson",
      "slides": [
        {
          "elements": [
            {
              "text": "Discover",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        },
        {
          "elements": [
            {
              "text": "Experiment",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        }
      ]
    },
    "slides-2": {
      "name": "Two-part lesson",
      "slides": [
        {
          "elements": [
            {
              "text": "Discover",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        },
        {
          "elements": [
            {
              "text": "Experiment",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        }
      ]
    }
  }
}

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 deck = SlidesApp.create("Two-part lesson");
  deck.getSlides()[0].insertTextBox("Discover");
  deck.appendSlide(SlidesApp.PredefinedLayout.BLANK).insertTextBox("Experiment");
}
function main() {
  console.log("Start: Creating presentations and slides");
  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 deck = SlidesApp.create("Two-part lesson");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: deck.getSlides()[0].insertTextBox("Discover");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: deck.appendSlide(SlidesApp.PredefinedLayout.BLANK).insertTextBox("Experiment");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
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 presentations and slides");
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 presentations and slides",
    "Completed operation"
  ],
  "error": null,
  "resource": "presentations",
  "value": {
    "slides-1": {
      "name": "Two-part lesson",
      "slides": [
        {
          "elements": [
            {
              "text": "Discover",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        },
        {
          "elements": [
            {
              "text": "Experiment",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        }
      ]
    }
  }
}

Build and test

Repair the supplied script so that: The default slide introduces Discover and the appended blank slide introduces Experiment. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  const deck = SlidesApp.create("Two-part lesson");
  deck.getSlides()[0].insertTextBox("Discover");
  deck.appendSlide(SlidesApp.PredefinedLayout.BLANK).insertTextBox("Wrong section");
}

Graduated hints

Hint 1

Inspect the operation containing "Wrong section". Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns "Experiment". Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses "Experiment" where the broken source uses "Wrong section". Explain why before applying it.

Reference solution

function main() {
  const deck = SlidesApp.create("Two-part lesson");
  deck.getSlides()[0].insertTextBox("Discover");
  deck.appendSlide(SlidesApp.PredefinedLayout.BLANK).insertTextBox("Experiment");
}

Explain and reflect

Which operation proves the intended result in creating presentations and slides? Which wrong input would expose a weakness, and what would remain unchanged?

Adapt the input records and presentations 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 presentations 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: Text, shapes and page coordinates