36. Drive files, folders and IDs
Module 8 · 20 minutes · Lesson 35; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use drive files, folders and ids without changing the wrong data?
- Explain drive files, folders and ids in your own words
- Trace the actual console result 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 ID identifies one resource while a name can be duplicated. A folder is a container, not a path string accepted by getFileById. Access depends on the executing account’s permissions. Store validated IDs in configuration and show clear errors for missing resources. The local tree uses stable fictional IDs and has no connection to Drive.
Example 1: Working automation
The stable ID returns the correct file even if its visible name later changes.
function main() {
const file = DriveApp.getFileById("brief");
console.log(file.getId());
console.log(file.getName());
console.log(file.getMimeType());
}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 file = DriveApp.getFileById("brief");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: console.log(file.getId());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: console.log(file.getName());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: console.log(file.getMimeType());
- 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": [
"brief",
"Brief.txt",
"text/plain"
],
"error": null,
"resource": "logs",
"value": null
}Example 2: Investigate a reproducible failure
Predict the effect of getFileById("missing") and identify the first mismatch. This example is intentionally faulty.
function main() {
const file = DriveApp.getFileById("missing");
console.log(file.getId());
console.log(file.getName());
console.log(file.getMimeType());
}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 file = DriveApp.getFileById("missing");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: console.log(file.getId());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: console.log(file.getName());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: console.log(file.getMimeType());
- 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": [],
"error": "File not found: missing",
"resource": "logs",
"value": null
}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 file = DriveApp.getFileById("brief");
console.log(file.getId());
console.log(file.getName());
console.log(file.getMimeType());
}
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 file = DriveApp.getFileById("brief");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: console.log(file.getId());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: console.log(file.getName());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: console.log(file.getMimeType());
- 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": [
"brief",
"Brief.txt",
"text/plain",
"brief",
"Brief.txt",
"text/plain"
],
"error": null,
"resource": "logs",
"value": null
}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 file = DriveApp.getFileById("brief");
console.log(file.getId());
console.log(file.getName());
console.log(file.getMimeType());
}
function main() {
console.log("Start: Drive files, folders and IDs");
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 file = DriveApp.getFileById("brief");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: console.log(file.getId());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: console.log(file.getName());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: console.log(file.getMimeType());
- 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: Drive files, folders and IDs");
- 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: Drive files, folders and IDs",
"brief",
"Brief.txt",
"text/plain",
"Completed operation"
],
"error": null,
"resource": "logs",
"value": null
}Build and test
Repair the supplied script so that: The stable ID returns the correct file even if its visible name later changes. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const file = DriveApp.getFileById("missing");
console.log(file.getId());
console.log(file.getName());
console.log(file.getMimeType());
}Graduated hints
Hint 1
Inspect the operation containing getFileById("missing"). Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns getFileById("brief"). Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses getFileById("brief") where the broken source uses getFileById("missing"). Explain why before applying it.
Reference solution
function main() {
const file = DriveApp.getFileById("brief");
console.log(file.getId());
console.log(file.getName());
console.log(file.getMimeType());
}Explain and reflect
Which operation proves the intended result in drive files, folders and ids? Which wrong input would expose a weakness, and what would remain unchanged?
Adapt the calculation or validation 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 logs 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.