4. Writing and running your first script
Module 1 · 20 minutes · Lesson 3; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use writing and running your first script without changing the wrong data?
- Explain writing and running your first script in your own words
- Trace the actual sheets 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 method is a function accessed through an object. Parentheses invoke it, and arguments supply values. const gives the returned sheet a reusable local name; it does not freeze the sheet’s contents. The quoted address is text interpreted by getRange. After changing one address, rerun against fresh sample data and compare the highlighted write. Google execution requires a spreadsheet-bound context or an explicit workbook ID.
Example 1: Working automation
The getter reads the value written earlier in the same run, so the console confirms the state change.
function main() {
const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
sheet.getRange("B3").setValue("Complete");
console.log(sheet.getRange("B3").getValue());
}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().getActiveSheet();
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 3: sheet.getRange("B3").setValue("Complete");
- Select a rectangular area. A1 letters name columns; row and numeric range coordinates start at one.
- Line 4: console.log(sheet.getRange("B3").getValue());
- Select a rectangular area. A1 letters name columns; row and numeric range coordinates start at one.
- Line 5: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Complete"
],
"error": null,
"resource": "sheets",
"value": {
"People": [
[
"Name",
"Status"
],
[
"Alex",
"Pending"
],
[
"Jordan",
"Complete"
],
[
"Morgan",
"Pending"
]
],
"Sales": [
[
"Customer",
"Amount",
"Approved"
],
[
"Alex",
120,
true
],
[
"Jordan",
80,
false
],
[
"Morgan",
200,
true
]
],
"Tasks": [
[
"Task",
"Status"
],
[
"Review invoice",
"Open"
],
[
"Publish report",
"Complete"
]
]
}
}Example 2: Investigate a reproducible failure
Predict the effect of setValue("Pending") and identify the first mismatch. This example is intentionally faulty.
function main() {
const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
sheet.getRange("B3").setValue("Pending");
console.log(sheet.getRange("B3").getValue());
}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().getActiveSheet();
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 3: sheet.getRange("B3").setValue("Pending");
- Select a rectangular area. A1 letters name columns; row and numeric range coordinates start at one.
- Line 4: console.log(sheet.getRange("B3").getValue());
- Select a rectangular area. A1 letters name columns; row and numeric range coordinates start at one.
- Line 5: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Pending"
],
"error": null,
"resource": "sheets",
"value": {
"People": [
[
"Name",
"Status"
],
[
"Alex",
"Pending"
],
[
"Jordan",
"Pending"
],
[
"Morgan",
"Pending"
]
],
"Sales": [
[
"Customer",
"Amount",
"Approved"
],
[
"Alex",
120,
true
],
[
"Jordan",
80,
false
],
[
"Morgan",
200,
true
]
],
"Tasks": [
[
"Task",
"Status"
],
[
"Review invoice",
"Open"
],
[
"Publish report",
"Complete"
]
]
}
}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().getActiveSheet();
sheet.getRange("B3").setValue("Complete");
console.log(sheet.getRange("B3").getValue());
}
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().getActiveSheet();
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 3: sheet.getRange("B3").setValue("Complete");
- Select a rectangular area. A1 letters name columns; row and numeric range coordinates start at one.
- Line 4: console.log(sheet.getRange("B3").getValue());
- Select a rectangular area. A1 letters name columns; row and numeric range coordinates start at one.
- 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": [
"Complete",
"Complete"
],
"error": null,
"resource": "sheets",
"value": {
"People": [
[
"Name",
"Status"
],
[
"Alex",
"Pending"
],
[
"Jordan",
"Complete"
],
[
"Morgan",
"Pending"
]
],
"Sales": [
[
"Customer",
"Amount",
"Approved"
],
[
"Alex",
120,
true
],
[
"Jordan",
80,
false
],
[
"Morgan",
200,
true
]
],
"Tasks": [
[
"Task",
"Status"
],
[
"Review invoice",
"Open"
],
[
"Publish report",
"Complete"
]
]
}
}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().getActiveSheet();
sheet.getRange("B3").setValue("Complete");
console.log(sheet.getRange("B3").getValue());
}
function main() {
console.log("Start: Writing and running your first script");
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().getActiveSheet();
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 3: sheet.getRange("B3").setValue("Complete");
- Select a rectangular area. A1 letters name columns; row and numeric range coordinates start at one.
- Line 4: console.log(sheet.getRange("B3").getValue());
- Select a rectangular area. A1 letters name columns; row and numeric range coordinates start at one.
- 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: Writing and running your first script");
- 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: Writing and running your first script",
"Complete",
"Completed operation"
],
"error": null,
"resource": "sheets",
"value": {
"People": [
[
"Name",
"Status"
],
[
"Alex",
"Pending"
],
[
"Jordan",
"Complete"
],
[
"Morgan",
"Pending"
]
],
"Sales": [
[
"Customer",
"Amount",
"Approved"
],
[
"Alex",
120,
true
],
[
"Jordan",
80,
false
],
[
"Morgan",
200,
true
]
],
"Tasks": [
[
"Task",
"Status"
],
[
"Review invoice",
"Open"
],
[
"Publish report",
"Complete"
]
]
}
}Build and test
Repair the supplied script so that: The getter reads the value written earlier in the same run, so the console confirms the state change. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
sheet.getRange("B3").setValue("Pending");
console.log(sheet.getRange("B3").getValue());
}Graduated hints
Hint 1
Inspect the operation containing setValue("Pending"). Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns setValue("Complete"). Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses setValue("Complete") where the broken source uses setValue("Pending"). Explain why before applying it.
Reference solution
function main() {
const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
sheet.getRange("B3").setValue("Complete");
console.log(sheet.getRange("B3").getValue());
}Explain and reflect
Which operation proves the intended result in writing and running your first script? Which wrong input would expose a weakness, and what would remain unchanged?
Adapt the input records and sheets 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 sheets 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.