24. Searching, filtering and transforming records
Module 5 · 20 minutes · Lesson 23; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use searching, filtering and transforming records without changing the wrong data?
- Explain searching, filtering and transforming records 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
Separate selection from mutation. Read rows, exclude headers, apply a predicate and create a clear output representation. Filtering an array does not delete source records. To write results, choose a destination and handle an empty match set. Compare types explicitly; the approved column contains Boolean values, not the text true.
Example 1: Working automation
Only Alex and Morgan have a Boolean approval. Comparing to a string finds no records.
function main() {
const sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
const records = sheet.getDataRange().getValues().slice(1);
const approved = records.filter(row => row[2] === true);
console.log(approved.map(row => 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 records = sheet.getDataRange().getValues().slice(1);
- Read a two-dimensional row/column array. JavaScript indices begin at zero, unlike sheet coordinates.
- Line 4: const approved = records.filter(row => row[2] === true);
- Create a new array containing only records that satisfy the predicate; this does not delete source rows.
- Line 5: console.log(approved.map(row => row[0]));
- 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": [
"[\"Alex\",\"Morgan\"]"
],
"error": null,
"resource": "logs",
"value": null
}Example 2: Investigate a reproducible failure
Predict the effect of row[2] === "true" and identify the first mismatch. This example is intentionally faulty.
function main() {
const sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
const records = sheet.getDataRange().getValues().slice(1);
const approved = records.filter(row => row[2] === "true");
console.log(approved.map(row => 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 records = sheet.getDataRange().getValues().slice(1);
- Read a two-dimensional row/column array. JavaScript indices begin at zero, unlike sheet coordinates.
- Line 4: const approved = records.filter(row => row[2] === "true");
- Create a new array containing only records that satisfy the predicate; this does not delete source rows.
- Line 5: console.log(approved.map(row => row[0]));
- 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": null,
"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 sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
const records = sheet.getDataRange().getValues().slice(1);
const approved = records.filter(row => row[2] === true);
console.log(approved.map(row => row[0]));
}
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 records = sheet.getDataRange().getValues().slice(1);
- Read a two-dimensional row/column array. JavaScript indices begin at zero, unlike sheet coordinates.
- Line 4: const approved = records.filter(row => row[2] === true);
- Create a new array containing only records that satisfy the predicate; this does not delete source rows.
- Line 5: console.log(approved.map(row => row[0]));
- 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": [
"[\"Alex\",\"Morgan\"]",
"[\"Alex\",\"Morgan\"]"
],
"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 sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
const records = sheet.getDataRange().getValues().slice(1);
const approved = records.filter(row => row[2] === true);
console.log(approved.map(row => row[0]));
}
function main() {
console.log("Start: Searching, filtering and transforming records");
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 records = sheet.getDataRange().getValues().slice(1);
- Read a two-dimensional row/column array. JavaScript indices begin at zero, unlike sheet coordinates.
- Line 4: const approved = records.filter(row => row[2] === true);
- Create a new array containing only records that satisfy the predicate; this does not delete source rows.
- Line 5: console.log(approved.map(row => row[0]));
- 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: Searching, filtering and transforming records");
- 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: Searching, filtering and transforming records",
"[\"Alex\",\"Morgan\"]",
"Completed operation"
],
"error": null,
"resource": "logs",
"value": null
}Build and test
Repair the supplied script so that: Only Alex and Morgan have a Boolean approval. Comparing to a string finds no records. 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 records = sheet.getDataRange().getValues().slice(1);
const approved = records.filter(row => row[2] === "true");
console.log(approved.map(row => row[0]));
}Graduated hints
Hint 1
Inspect the operation containing row[2] === "true". Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns row[2] === true. Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses row[2] === true where the broken source uses row[2] === "true". Explain why before applying it.
Reference solution
function main() {
const sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Sales");
const records = sheet.getDataRange().getValues().slice(1);
const approved = records.filter(row => row[2] === true);
console.log(approved.map(row => row[0]));
}Explain and reflect
Which operation proves the intended result in searching, filtering and transforming records? 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.