70. Connecting HTML to server functions
Module 14 · 20 minutes · Lesson 69; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use connecting html to server functions without changing the wrong data?
- Explain connecting html to server functions 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
google.script.run is asynchronous and returns control before the server result arrives. Register success and failure handlers, pass supported serializable data, and update the page in the callback. Server functions ending in an underscore are private to client calls. The server example returns data; open the Web Application Studio to exercise the paired client.
Example 1: Working automation
The callable server function returns all three people without the header, ready for a client success handler.
function main() {
console.log(getPeople());
}
function getPeople() {
return SpreadsheetApp.getActiveSpreadsheet().getSheetByName("People").getDataRange().getValues().slice(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: console.log(getPeople());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 3: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 4: function getPeople() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 5: return SpreadsheetApp.getActiveSpreadsheet().getSheetByName("People").getDataRange().getValues().slice(1);
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 6: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"[[\"Alex\",\"Pending\"],[\"Jordan\",\"Pending\"],[\"Morgan\",\"Pending\"]]"
],
"error": null,
"resource": "logs",
"value": null
}Example 2: Investigate a reproducible failure
Predict the effect of slice(2) and identify the first mismatch. This example is intentionally faulty.
function main() {
console.log(getPeople());
}
function getPeople() {
return SpreadsheetApp.getActiveSpreadsheet().getSheetByName("People").getDataRange().getValues().slice(2);
}Important line explanations
- Line 1: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: console.log(getPeople());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 3: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 4: function getPeople() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 5: return SpreadsheetApp.getActiveSpreadsheet().getSheetByName("People").getDataRange().getValues().slice(2);
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 6: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"[[\"Jordan\",\"Pending\"],[\"Morgan\",\"Pending\"]]"
],
"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() {
console.log(getPeople());
}
function getPeople() {
return SpreadsheetApp.getActiveSpreadsheet().getSheetByName("People").getDataRange().getValues().slice(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: console.log(getPeople());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 3: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 4: function getPeople() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 5: return SpreadsheetApp.getActiveSpreadsheet().getSheetByName("People").getDataRange().getValues().slice(1);
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- 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\",\"Pending\"],[\"Jordan\",\"Pending\"],[\"Morgan\",\"Pending\"]]",
"[[\"Alex\",\"Pending\"],[\"Jordan\",\"Pending\"],[\"Morgan\",\"Pending\"]]"
],
"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() {
console.log(getPeople());
}
function getPeople() {
return SpreadsheetApp.getActiveSpreadsheet().getSheetByName("People").getDataRange().getValues().slice(1);
}
function main() {
console.log("Start: Connecting HTML to server functions");
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: console.log(getPeople());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 3: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 4: function getPeople() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 5: return SpreadsheetApp.getActiveSpreadsheet().getSheetByName("People").getDataRange().getValues().slice(1);
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- 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: Connecting HTML to server functions");
- 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: Connecting HTML to server functions",
"[[\"Alex\",\"Pending\"],[\"Jordan\",\"Pending\"],[\"Morgan\",\"Pending\"]]",
"Completed operation"
],
"error": null,
"resource": "logs",
"value": null
}Build and test
Repair the supplied script so that: The callable server function returns all three people without the header, ready for a client success handler. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
console.log(getPeople());
}
function getPeople() {
return SpreadsheetApp.getActiveSpreadsheet().getSheetByName("People").getDataRange().getValues().slice(2);
}Graduated hints
Hint 1
Inspect the operation containing slice(2). Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns slice(1). Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses slice(1) where the broken source uses slice(2). Explain why before applying it.
Reference solution
function main() {
console.log(getPeople());
}
function getPeople() {
return SpreadsheetApp.getActiveSpreadsheet().getSheetByName("People").getDataRange().getValues().slice(1);
}Explain and reflect
Which operation proves the intended result in connecting html to server functions? 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.