35. Personalized documents from spreadsheet rows
Module 7 · 20 minutes · Lesson 34; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use personalized documents from spreadsheet rows without changing the wrong data?
- Explain personalized documents from spreadsheet rows in your own words
- Trace the actual docs 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
Read source records once and create one document per intended record. Give each output a meaningful name and record its ID for recovery. Large batches need checkpoints and duplicate protection. A document generated with the wrong column mapping can look plausible, so verify actual names and amounts in the outputs, not merely the file count.
Example 1: Working automation
Each customer gets a distinct document derived from the corresponding row, without altering Sales.
function main() {
const sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
const rows = sheet.getDataRange().getValues().slice(1);
rows.forEach(row => {
const doc = DocumentApp.create("Statement - " + row[0]);
doc.getTabs()[0].asDocumentTab().getBody().appendParagraph(row[0] + " owes " + row[1]);
});
}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 sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 3: const rows = sheet.getDataRange().getValues().slice(1);
- Read a two-dimensional row/column array. JavaScript indices begin at zero, unlike sheet coordinates.
- Line 4: rows.forEach(row => {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 5: const doc = DocumentApp.create("Statement - " + row[0]);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 6: doc.getTabs()[0].asDocumentTab().getBody().appendParagraph(row[0] + " owes " + row[1]);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 7: });
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "docs",
"value": {
"template": {
"name": "Letter template",
"paragraphs": [
"Dear {{NAME}},",
"Your project {{PROJECT}} is scheduled for completion on {{DATE}}."
]
},
"doc-1": {
"name": "Statement - Alex",
"paragraphs": [
"Alex owes 120"
]
},
"doc-2": {
"name": "Statement - Jordan",
"paragraphs": [
"Jordan owes 80"
]
},
"doc-3": {
"name": "Statement - Morgan",
"paragraphs": [
"Morgan owes 200"
]
}
}
}Example 2: Investigate a reproducible failure
Predict the effect of row[1] + " owes " + row[0] and identify the first mismatch. This example is intentionally faulty.
function main() {
const sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
const rows = sheet.getDataRange().getValues().slice(1);
rows.forEach(row => {
const doc = DocumentApp.create("Statement - " + row[0]);
doc.getTabs()[0].asDocumentTab().getBody().appendParagraph(row[1] + " owes " + row[0]);
});
}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 sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 3: const rows = sheet.getDataRange().getValues().slice(1);
- Read a two-dimensional row/column array. JavaScript indices begin at zero, unlike sheet coordinates.
- Line 4: rows.forEach(row => {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 5: const doc = DocumentApp.create("Statement - " + row[0]);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 6: doc.getTabs()[0].asDocumentTab().getBody().appendParagraph(row[1] + " owes " + row[0]);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 7: });
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "docs",
"value": {
"template": {
"name": "Letter template",
"paragraphs": [
"Dear {{NAME}},",
"Your project {{PROJECT}} is scheduled for completion on {{DATE}}."
]
},
"doc-1": {
"name": "Statement - Alex",
"paragraphs": [
"120 owes Alex"
]
},
"doc-2": {
"name": "Statement - Jordan",
"paragraphs": [
"80 owes Jordan"
]
},
"doc-3": {
"name": "Statement - Morgan",
"paragraphs": [
"200 owes Morgan"
]
}
}
}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 sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
const rows = sheet.getDataRange().getValues().slice(1);
rows.forEach(row => {
const doc = DocumentApp.create("Statement - " + row[0]);
doc.getTabs()[0].asDocumentTab().getBody().appendParagraph(row[0] + " owes " + row[1]);
});
}
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 sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 3: const rows = sheet.getDataRange().getValues().slice(1);
- Read a two-dimensional row/column array. JavaScript indices begin at zero, unlike sheet coordinates.
- Line 4: rows.forEach(row => {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 5: const doc = DocumentApp.create("Statement - " + row[0]);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 6: doc.getTabs()[0].asDocumentTab().getBody().appendParagraph(row[0] + " owes " + row[1]);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 7: });
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 9: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 10: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 11: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 12: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "docs",
"value": {
"template": {
"name": "Letter template",
"paragraphs": [
"Dear {{NAME}},",
"Your project {{PROJECT}} is scheduled for completion on {{DATE}}."
]
},
"doc-1": {
"name": "Statement - Alex",
"paragraphs": [
"Alex owes 120"
]
},
"doc-2": {
"name": "Statement - Jordan",
"paragraphs": [
"Jordan owes 80"
]
},
"doc-3": {
"name": "Statement - Morgan",
"paragraphs": [
"Morgan owes 200"
]
},
"doc-4": {
"name": "Statement - Alex",
"paragraphs": [
"Alex owes 120"
]
},
"doc-5": {
"name": "Statement - Jordan",
"paragraphs": [
"Jordan owes 80"
]
},
"doc-6": {
"name": "Statement - Morgan",
"paragraphs": [
"Morgan owes 200"
]
}
}
}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 sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
const rows = sheet.getDataRange().getValues().slice(1);
rows.forEach(row => {
const doc = DocumentApp.create("Statement - " + row[0]);
doc.getTabs()[0].asDocumentTab().getBody().appendParagraph(row[0] + " owes " + row[1]);
});
}
function main() {
console.log("Start: Personalized documents from spreadsheet rows");
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 sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 3: const rows = sheet.getDataRange().getValues().slice(1);
- Read a two-dimensional row/column array. JavaScript indices begin at zero, unlike sheet coordinates.
- Line 4: rows.forEach(row => {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 5: const doc = DocumentApp.create("Statement - " + row[0]);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 6: doc.getTabs()[0].asDocumentTab().getBody().appendParagraph(row[0] + " owes " + row[1]);
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 7: });
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 9: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 10: console.log("Start: Personalized documents from spreadsheet rows");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 11: try { lessonAction(); console.log("Completed operation"); }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 12: 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 13: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Start: Personalized documents from spreadsheet rows",
"Completed operation"
],
"error": null,
"resource": "docs",
"value": {
"template": {
"name": "Letter template",
"paragraphs": [
"Dear {{NAME}},",
"Your project {{PROJECT}} is scheduled for completion on {{DATE}}."
]
},
"doc-1": {
"name": "Statement - Alex",
"paragraphs": [
"Alex owes 120"
]
},
"doc-2": {
"name": "Statement - Jordan",
"paragraphs": [
"Jordan owes 80"
]
},
"doc-3": {
"name": "Statement - Morgan",
"paragraphs": [
"Morgan owes 200"
]
}
}
}Build and test
Repair the supplied script so that: Each customer gets a distinct document derived from the corresponding row, without altering Sales. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
const rows = sheet.getDataRange().getValues().slice(1);
rows.forEach(row => {
const doc = DocumentApp.create("Statement - " + row[0]);
doc.getTabs()[0].asDocumentTab().getBody().appendParagraph(row[1] + " owes " + row[0]);
});
}Graduated hints
Hint 1
Inspect the operation containing row[1] + " owes " + row[0]. Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns row[0] + " owes " + row[1]. Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses row[0] + " owes " + row[1] where the broken source uses row[1] + " owes " + row[0]. Explain why before applying it.
Reference solution
function main() {
const sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
const rows = sheet.getDataRange().getValues().slice(1);
rows.forEach(row => {
const doc = DocumentApp.create("Statement - " + row[0]);
doc.getTabs()[0].asDocumentTab().getBody().appendParagraph(row[0] + " owes " + row[1]);
});
}Explain and reflect
Which operation proves the intended result in personalized documents from spreadsheet rows? Which wrong input would expose a weakness, and what would remain unchanged?
Adapt the input records and docs 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 docs 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.