DiscoveryVIP / Apps Script AcademyHelp

38. Creating, copying, renaming and moving files

Module 8 · 20 minutes · Lesson 37; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use creating, copying, renaming and moving files without changing the wrong data?

Predict

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

Understand

Copying makes a new resource; renaming or moving changes an existing one. Keep source and destination IDs separate. A safe organizer validates the destination before changing a file and records an audit trail. The academy’s Undo Simulation restores local state; real Drive operations require their own recovery plan.

Example 1: Working automation

A new file is created inside Archive and renamed; the original brief remains in the root.

function main() {
  const folder = DriveApp.createFolder("Archive");
  const copy = DriveApp.getFileById("brief").makeCopy("Brief copy", folder);
  copy.setName("Reviewed brief");
}
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 folder = DriveApp.createFolder("Archive");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: const copy = DriveApp.getFileById("brief").makeCopy("Brief copy", folder);
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 4: copy.setName("Reviewed brief");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": null,
  "resource": "files",
  "value": {
    "brief": {
      "name": "Brief.txt",
      "folder": "root",
      "content": "Sample project brief",
      "sharing": "PRIVATE"
    },
    "template": {
      "name": "Letter template",
      "folder": "root",
      "content": "",
      "sharing": "PRIVATE"
    },
    "file-2": {
      "name": "Reviewed brief",
      "folder": "folder-1",
      "content": "Sample project brief",
      "sharing": "PRIVATE"
    }
  }
}

Example 2: Investigate a reproducible failure

Predict the effect of copy.setName("Unreviewed brief") and identify the first mismatch. This example is intentionally faulty.

function main() {
  const folder = DriveApp.createFolder("Archive");
  const copy = DriveApp.getFileById("brief").makeCopy("Brief copy", folder);
  copy.setName("Unreviewed brief");
}
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 folder = DriveApp.createFolder("Archive");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: const copy = DriveApp.getFileById("brief").makeCopy("Brief copy", folder);
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 4: copy.setName("Unreviewed brief");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": null,
  "resource": "files",
  "value": {
    "brief": {
      "name": "Brief.txt",
      "folder": "root",
      "content": "Sample project brief",
      "sharing": "PRIVATE"
    },
    "template": {
      "name": "Letter template",
      "folder": "root",
      "content": "",
      "sharing": "PRIVATE"
    },
    "file-2": {
      "name": "Unreviewed brief",
      "folder": "folder-1",
      "content": "Sample project brief",
      "sharing": "PRIVATE"
    }
  }
}

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 folder = DriveApp.createFolder("Archive");
  const copy = DriveApp.getFileById("brief").makeCopy("Brief copy", folder);
  copy.setName("Reviewed brief");
}
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 folder = DriveApp.createFolder("Archive");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: const copy = DriveApp.getFileById("brief").makeCopy("Brief copy", folder);
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 4: copy.setName("Reviewed brief");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
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": "files",
  "value": {
    "brief": {
      "name": "Brief.txt",
      "folder": "root",
      "content": "Sample project brief",
      "sharing": "PRIVATE"
    },
    "template": {
      "name": "Letter template",
      "folder": "root",
      "content": "",
      "sharing": "PRIVATE"
    },
    "file-2": {
      "name": "Reviewed brief",
      "folder": "folder-1",
      "content": "Sample project brief",
      "sharing": "PRIVATE"
    },
    "file-4": {
      "name": "Reviewed brief",
      "folder": "folder-3",
      "content": "Sample project brief",
      "sharing": "PRIVATE"
    }
  }
}

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 folder = DriveApp.createFolder("Archive");
  const copy = DriveApp.getFileById("brief").makeCopy("Brief copy", folder);
  copy.setName("Reviewed brief");
}
function main() {
  console.log("Start: Creating, copying, renaming and moving files");
  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 folder = DriveApp.createFolder("Archive");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: const copy = DriveApp.getFileById("brief").makeCopy("Brief copy", folder);
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 4: copy.setName("Reviewed brief");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
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, copying, renaming and moving files");
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, copying, renaming and moving files",
    "Completed operation"
  ],
  "error": null,
  "resource": "files",
  "value": {
    "brief": {
      "name": "Brief.txt",
      "folder": "root",
      "content": "Sample project brief",
      "sharing": "PRIVATE"
    },
    "template": {
      "name": "Letter template",
      "folder": "root",
      "content": "",
      "sharing": "PRIVATE"
    },
    "file-2": {
      "name": "Reviewed brief",
      "folder": "folder-1",
      "content": "Sample project brief",
      "sharing": "PRIVATE"
    }
  }
}

Build and test

Repair the supplied script so that: A new file is created inside Archive and renamed; the original brief remains in the root. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  const folder = DriveApp.createFolder("Archive");
  const copy = DriveApp.getFileById("brief").makeCopy("Brief copy", folder);
  copy.setName("Unreviewed brief");
}

Graduated hints

Hint 1

Inspect the operation containing copy.setName("Unreviewed brief"). Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns copy.setName("Reviewed brief"). Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses copy.setName("Reviewed brief") where the broken source uses copy.setName("Unreviewed brief"). Explain why before applying it.

Reference solution

function main() {
  const folder = DriveApp.createFolder("Archive");
  const copy = DriveApp.getFileById("brief").makeCopy("Brief copy", folder);
  copy.setName("Reviewed brief");
}

Explain and reflect

Which operation proves the intended result in creating, copying, renaming and moving files? Which wrong input would expose a weakness, and what would remain unchanged?

Adapt the input records and files 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 files 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: Metadata and permissions