DiscoveryVIP / Apps Script AcademyHelp

58. Text, shapes and page coordinates

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

Open Interactive Lesson

Discover

How can you use text, shapes and page coordinates without changing the wrong data?

Predict

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

Understand

Each page element needs a position and size consistent with the page. Text content and geometry are separate concerns. The simulator supports text boxes and rectangles; image insertion is provided as a real-environment reference rather than a pretend image fetch. Prefer simple diagrams with readable labels and sufficient contrast.

Example 1: Working automation

The title and labeled rectangle occupy distinct coordinates rather than overlapping at a default location.

function main() {
  const slide = SlidesApp.create("Process diagram").getSlides()[0];
  slide.insertTextBox("Input → Process → Output", 20, 20, 600, 80);
  slide.insertShape(SlidesApp.ShapeType.RECTANGLE, 20, 120, 200, 80).getText().setText("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 slide = SlidesApp.create("Process diagram").getSlides()[0];
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: slide.insertTextBox("Input → Process → Output", 20, 20, 600, 80);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: slide.insertShape(SlidesApp.ShapeType.RECTANGLE, 20, 120, 200, 80).getText().setText("Review");
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": "Process diagram",
      "slides": [
        {
          "elements": [
            {
              "text": "Input \u2192 Process \u2192 Output",
              "left": 20,
              "top": 20,
              "width": 600,
              "height": 80
            },
            {
              "type": "RECTANGLE",
              "left": 20,
              "top": 120,
              "width": 200,
              "height": 80,
              "text": "Review"
            }
          ]
        }
      ]
    }
  }
}

Example 2: Investigate a reproducible failure

Predict the effect of setText("Skip review") and identify the first mismatch. This example is intentionally faulty.

function main() {
  const slide = SlidesApp.create("Process diagram").getSlides()[0];
  slide.insertTextBox("Input → Process → Output", 20, 20, 600, 80);
  slide.insertShape(SlidesApp.ShapeType.RECTANGLE, 20, 120, 200, 80).getText().setText("Skip 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 slide = SlidesApp.create("Process diagram").getSlides()[0];
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: slide.insertTextBox("Input → Process → Output", 20, 20, 600, 80);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: slide.insertShape(SlidesApp.ShapeType.RECTANGLE, 20, 120, 200, 80).getText().setText("Skip review");
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": "Process diagram",
      "slides": [
        {
          "elements": [
            {
              "text": "Input \u2192 Process \u2192 Output",
              "left": 20,
              "top": 20,
              "width": 600,
              "height": 80
            },
            {
              "type": "RECTANGLE",
              "left": 20,
              "top": 120,
              "width": 200,
              "height": 80,
              "text": "Skip review"
            }
          ]
        }
      ]
    }
  }
}

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 slide = SlidesApp.create("Process diagram").getSlides()[0];
  slide.insertTextBox("Input → Process → Output", 20, 20, 600, 80);
  slide.insertShape(SlidesApp.ShapeType.RECTANGLE, 20, 120, 200, 80).getText().setText("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 slide = SlidesApp.create("Process diagram").getSlides()[0];
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: slide.insertTextBox("Input → Process → Output", 20, 20, 600, 80);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: slide.insertShape(SlidesApp.ShapeType.RECTANGLE, 20, 120, 200, 80).getText().setText("Review");
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": "Process diagram",
      "slides": [
        {
          "elements": [
            {
              "text": "Input \u2192 Process \u2192 Output",
              "left": 20,
              "top": 20,
              "width": 600,
              "height": 80
            },
            {
              "type": "RECTANGLE",
              "left": 20,
              "top": 120,
              "width": 200,
              "height": 80,
              "text": "Review"
            }
          ]
        }
      ]
    },
    "slides-2": {
      "name": "Process diagram",
      "slides": [
        {
          "elements": [
            {
              "text": "Input \u2192 Process \u2192 Output",
              "left": 20,
              "top": 20,
              "width": 600,
              "height": 80
            },
            {
              "type": "RECTANGLE",
              "left": 20,
              "top": 120,
              "width": 200,
              "height": 80,
              "text": "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 slide = SlidesApp.create("Process diagram").getSlides()[0];
  slide.insertTextBox("Input → Process → Output", 20, 20, 600, 80);
  slide.insertShape(SlidesApp.ShapeType.RECTANGLE, 20, 120, 200, 80).getText().setText("Review");
}
function main() {
  console.log("Start: Text, shapes and page coordinates");
  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 slide = SlidesApp.create("Process diagram").getSlides()[0];
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: slide.insertTextBox("Input → Process → Output", 20, 20, 600, 80);
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: slide.insertShape(SlidesApp.ShapeType.RECTANGLE, 20, 120, 200, 80).getText().setText("Review");
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: Text, shapes and page coordinates");
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: Text, shapes and page coordinates",
    "Completed operation"
  ],
  "error": null,
  "resource": "presentations",
  "value": {
    "slides-1": {
      "name": "Process diagram",
      "slides": [
        {
          "elements": [
            {
              "text": "Input \u2192 Process \u2192 Output",
              "left": 20,
              "top": 20,
              "width": 600,
              "height": 80
            },
            {
              "type": "RECTANGLE",
              "left": 20,
              "top": 120,
              "width": 200,
              "height": 80,
              "text": "Review"
            }
          ]
        }
      ]
    }
  }
}

Build and test

Repair the supplied script so that: The title and labeled rectangle occupy distinct coordinates rather than overlapping at a default location. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  const slide = SlidesApp.create("Process diagram").getSlides()[0];
  slide.insertTextBox("Input → Process → Output", 20, 20, 600, 80);
  slide.insertShape(SlidesApp.ShapeType.RECTANGLE, 20, 120, 200, 80).getText().setText("Skip review");
}

Graduated hints

Hint 1

Inspect the operation containing setText("Skip review"). Compare it with the stated rule and the first mismatch.

Hint 2

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

Hint 3

The reference uses setText("Review") where the broken source uses setText("Skip review"). Explain why before applying it.

Reference solution

function main() {
  const slide = SlidesApp.create("Process diagram").getSlides()[0];
  slide.insertTextBox("Input → Process → Output", 20, 20, 600, 80);
  slide.insertShape(SlidesApp.ShapeType.RECTANGLE, 20, 120, 200, 80).getText().setText("Review");
}

Explain and reflect

Which operation proves the intended result in text, shapes and page coordinates? 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: Slides from spreadsheet records