40. File management workflows
Module 8 · 20 minutes · Lesson 39; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use file management workflows without changing the wrong data?
- Explain file management workflows in your own words
- Trace the actual files state change from the source
- Repair the supplied failing operation and verify the result
Predict
Which values or resources will change, and which should stay unchanged? Write your prediction before execution.
Understand
A file organizer should be repeatable and explicit about which resources it touches. Retrieve or create a destination, enumerate source files, filter candidates and move each intended file. This exercise copies into a new project folder to preserve inputs. In a real batch save a manifest of source and output IDs and test duplicate-name behavior.
Example 1: Working automation
The folder is reused if present. The source is copied, so repeated execution can still create duplicate copies to investigate.
function main() {
const matches = DriveApp.getFoldersByName("Project Alpha");
const folder = matches.hasNext() ? matches.next() : DriveApp.createFolder("Project Alpha");
DriveApp.getFileById("brief").makeCopy("Project brief", folder);
console.log(folder.getName());
}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 matches = DriveApp.getFoldersByName("Project Alpha");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const folder = matches.hasNext() ? matches.next() : DriveApp.createFolder("Project Alpha");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: DriveApp.getFileById("brief").makeCopy("Project brief", folder);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 5: console.log(folder.getName());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 6: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Project Alpha"
],
"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": "Project brief",
"folder": "folder-1",
"content": "Sample project brief",
"sharing": "PRIVATE"
}
}
}Example 2: Investigate a reproducible failure
Predict the effect of makeCopy("Wrong brief", folder) and identify the first mismatch. This example is intentionally faulty.
function main() {
const matches = DriveApp.getFoldersByName("Project Alpha");
const folder = matches.hasNext() ? matches.next() : DriveApp.createFolder("Project Alpha");
DriveApp.getFileById("brief").makeCopy("Wrong brief", folder);
console.log(folder.getName());
}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 matches = DriveApp.getFoldersByName("Project Alpha");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const folder = matches.hasNext() ? matches.next() : DriveApp.createFolder("Project Alpha");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: DriveApp.getFileById("brief").makeCopy("Wrong brief", folder);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 5: console.log(folder.getName());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 6: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Project Alpha"
],
"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": "Wrong 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 matches = DriveApp.getFoldersByName("Project Alpha");
const folder = matches.hasNext() ? matches.next() : DriveApp.createFolder("Project Alpha");
DriveApp.getFileById("brief").makeCopy("Project brief", folder);
console.log(folder.getName());
}
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 matches = DriveApp.getFoldersByName("Project Alpha");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const folder = matches.hasNext() ? matches.next() : DriveApp.createFolder("Project Alpha");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: DriveApp.getFileById("brief").makeCopy("Project brief", folder);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 5: console.log(folder.getName());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 6: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 7: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- 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: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 10: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Project Alpha",
"Project Alpha"
],
"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": "Project brief",
"folder": "folder-1",
"content": "Sample project brief",
"sharing": "PRIVATE"
},
"file-3": {
"name": "Project brief",
"folder": "folder-1",
"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 matches = DriveApp.getFoldersByName("Project Alpha");
const folder = matches.hasNext() ? matches.next() : DriveApp.createFolder("Project Alpha");
DriveApp.getFileById("brief").makeCopy("Project brief", folder);
console.log(folder.getName());
}
function main() {
console.log("Start: File management workflows");
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 matches = DriveApp.getFoldersByName("Project Alpha");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const folder = matches.hasNext() ? matches.next() : DriveApp.createFolder("Project Alpha");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: DriveApp.getFileById("brief").makeCopy("Project brief", folder);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 5: console.log(folder.getName());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 6: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 7: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 8: console.log("Start: File management workflows");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 9: try { lessonAction(); console.log("Completed operation"); }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 10: 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 11: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Start: File management workflows",
"Project Alpha",
"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": "Project brief",
"folder": "folder-1",
"content": "Sample project brief",
"sharing": "PRIVATE"
}
}
}Build and test
Repair the supplied script so that: The folder is reused if present. The source is copied, so repeated execution can still create duplicate copies to investigate. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const matches = DriveApp.getFoldersByName("Project Alpha");
const folder = matches.hasNext() ? matches.next() : DriveApp.createFolder("Project Alpha");
DriveApp.getFileById("brief").makeCopy("Wrong brief", folder);
console.log(folder.getName());
}Graduated hints
Hint 1
Inspect the operation containing makeCopy("Wrong brief", folder). Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns makeCopy("Project brief", folder). Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses makeCopy("Project brief", folder) where the broken source uses makeCopy("Wrong brief", folder). Explain why before applying it.
Reference solution
function main() {
const matches = DriveApp.getFoldersByName("Project Alpha");
const folder = matches.hasNext() ? matches.next() : DriveApp.createFolder("Project Alpha");
DriveApp.getFileById("brief").makeCopy("Project brief", folder);
console.log(folder.getName());
}Explain and reflect
Which operation proves the intended result in file management workflows? 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.