DiscoveryVIP / Apps Script AcademyHelp

56. Presentations, slides and page elements

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

Open Interactive Lesson

Discover

How can you use presentations, slides and page elements without changing the wrong data?

Predict

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

Understand

A presentation contains slides, each containing positioned page elements. Text boxes are elements with text ranges. The local preview shows structure and coordinates rather than reproducing Google’s rendering. New presentations start with a slide; choose whether to reuse it or append more. Position and size values are points, not CSS pixels in the Google API.

Example 1: Working automation

The first slide exists and receives a text box. No second slide exists until appended.

function main() {
  const deck = SlidesApp.create("Workshop deck");
  deck.getSlides()[0].insertTextBox("Welcome", 20, 20, 500, 80);
  console.log(deck.getSlides().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 deck = SlidesApp.create("Workshop deck");
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("Welcome", 20, 20, 500, 80);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: console.log(deck.getSlides().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": [
    "1"
  ],
  "error": null,
  "resource": "presentations",
  "value": {
    "slides-1": {
      "name": "Workshop deck",
      "slides": [
        {
          "elements": [
            {
              "text": "Welcome",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        }
      ]
    }
  }
}

Example 2: Investigate a reproducible failure

Predict the effect of getSlides()[1] and identify the first mismatch. This example is intentionally faulty.

function main() {
  const deck = SlidesApp.create("Workshop deck");
  deck.getSlides()[1].insertTextBox("Welcome", 20, 20, 500, 80);
  console.log(deck.getSlides().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 deck = SlidesApp.create("Workshop deck");
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()[1].insertTextBox("Welcome", 20, 20, 500, 80);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: console.log(deck.getSlides().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": "Cannot read properties of undefined (reading 'insertTextBox')",
  "resource": "presentations",
  "value": {
    "slides-1": {
      "name": "Workshop deck",
      "slides": [
        {
          "elements": []
        }
      ]
    }
  }
}

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("Workshop deck");
  deck.getSlides()[0].insertTextBox("Welcome", 20, 20, 500, 80);
  console.log(deck.getSlides().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 deck = SlidesApp.create("Workshop deck");
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("Welcome", 20, 20, 500, 80);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: console.log(deck.getSlides().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": [
    "1",
    "1"
  ],
  "error": null,
  "resource": "presentations",
  "value": {
    "slides-1": {
      "name": "Workshop deck",
      "slides": [
        {
          "elements": [
            {
              "text": "Welcome",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        }
      ]
    },
    "slides-2": {
      "name": "Workshop deck",
      "slides": [
        {
          "elements": [
            {
              "text": "Welcome",
              "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("Workshop deck");
  deck.getSlides()[0].insertTextBox("Welcome", 20, 20, 500, 80);
  console.log(deck.getSlides().length);
}
function main() {
  console.log("Start: Presentations, slides and page elements");
  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("Workshop deck");
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("Welcome", 20, 20, 500, 80);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: console.log(deck.getSlides().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: Presentations, slides and page elements");
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: Presentations, slides and page elements",
    "1",
    "Completed operation"
  ],
  "error": null,
  "resource": "presentations",
  "value": {
    "slides-1": {
      "name": "Workshop deck",
      "slides": [
        {
          "elements": [
            {
              "text": "Welcome",
              "left": 20,
              "top": 20,
              "width": 500,
              "height": 80
            }
          ]
        }
      ]
    }
  }
}

Build and test

Repair the supplied script so that: The first slide exists and receives a text box. No second slide exists until appended. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  const deck = SlidesApp.create("Workshop deck");
  deck.getSlides()[1].insertTextBox("Welcome", 20, 20, 500, 80);
  console.log(deck.getSlides().length);
}

Graduated hints

Hint 1

Inspect the operation containing getSlides()[1]. Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns getSlides()[0]. Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses getSlides()[0] where the broken source uses getSlides()[1]. Explain why before applying it.

Reference solution

function main() {
  const deck = SlidesApp.create("Workshop deck");
  deck.getSlides()[0].insertTextBox("Welcome", 20, 20, 500, 80);
  console.log(deck.getSlides().length);
}

Explain and reflect

Which operation proves the intended result in presentations, slides and page elements? 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: Creating presentations and slides