Zoho Sheet LAMBDA Function: Parameters, Direct Calls and Reuse
Define parameterized calculations with Zoho Sheet LAMBDA, compare direct calls, review named-function reuse and build explicit boundary checks.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
=LAMBDA(x;y;x+y)(3;4) defines a two-parameter addition and immediately calls it, returning 7. The first parentheses define names and a calculation; the second supply the actual inputs. Zoho also supports giving a LAMBDA a defined name for reuse.
Availability and version history
- Introduced: Added in September 2021, according to Zoho’s release history; no numbered cloud release is given.
- Availability: Listed in the current Zoho Sheet function reference; no final supported-version endpoint is documented.
- Scope: Zoho Sheet web-service documentation. Individual mobile, desktop/offline and imported-workbook behavior remains separately unverified.
- Checked: October 14, 2026, against the official LAMBDA entry. Outputs were independently calculated; no native Zoho Sheet execution was performed.
Syntax and direct invocation
Zoho prints the following general form:
LAMBDA(name; cal_or_name; [name]; [name2]...)
Its explanation and examples make the ordering clearer: list parameter names, then put the result calculation last. The direct two-input example is =LAMBDA(x;y;x+y)(A2;B2). The names x and y receive the values from A2 and B2 in that order. See the official LAMBDA reference.
The definition LAMBDA(x;y;x*y) describes a calculation; appending (A2;B2) supplies inputs for a direct cell result. Do not confuse a parameter name with a literal text value or assume that displaying a bare definition produces the same scalar result as calling it.
Build a direct-call comparison sheet
Create DirectCalls, with inputs x and y in A1:B1. Reserve C:H for sum, sum check, sum difference, product, product check and product difference. Enter:
| Row | A: first input | B: second input | Expected C and D: sum | Expected F and G: product |
|---|---|---|---|---|
| 2 | 3 | 4 | 7 | 12 |
| 3 | -2 | 5 | 3 | -10 |
| 4 | 0 | 7 | 7 | 0 |
| 5 | 2.5 | 1.5 | 4 | 3.75 |
| 6 | 100 | 0.1 | 100.1 | 10 |
Enter these formulas in row 2 and fill C2:H2 through row 6:
C2: =LAMBDA(x;y;x+y)(A2;B2)
D2: =A2+B2
E2: =C2-D2
F2: =LAMBDA(x;y;x*y)(A2;B2)
G2: =A2*B2
H2: =F2-G2
E and H are zero in the mathematical model. The definition is unchanged down the column, while the supplied cell references move. All printed outputs are independently calculated expectations, not observed runtime results.
Duplicate DirectCalls as ChangedArgument and change only B3 from 5 to 8. C3/D3 become 6 and F3/G3 −16. The other rows remain unchanged. Changing a call’s supplied input is different from editing the calculation inside the definition.
Argument order becomes visible with subtraction
Create OrderedInputs, with Revenue and Cost in A1:B1 and enter 100,70 in A2:B2 and 50,80 in A3:B3. Enter C2:F2 and fill through row 3:
C2: =LAMBDA(revenue;cost;revenue-cost)(A2;B2)
D2: =LAMBDA(revenue;cost;revenue-cost)(B2;A2)
E2: =A2-B2
F2: =C2+D2
C/E are 30,−30, D is −30,30, and F is zero. Renaming parameters to meaningful words helps document the order, but the function does not infer which supplied cell is revenue. Addition and multiplication would conceal this reversal because they are commutative.
A reusable commission definition
Zoho’s launch guide describes assigning RepCommission to =LAMBDA(sales;sales*10/100) through its defined-name feature. It also explains that editing that definition in the Define Name dialog updates uses of the named function.
First reproduce the arithmetic without creating any workbook names. On CommissionCalls, put numeric revenues 1000,2500,0 in A2:A4. Enter B2 =LAMBDA(sales;sales*10/100)(A2) and fill to B4: 100,250,0. In C2 enter =LAMBDA(sales;sales*15/100)(A2) and fill to C4: 150,375,0. D2 =C2-B2, filled through D4, gives 50,125,0.
If you then use Zoho’s documented naming workflow, a named call such as =RepCommission(A2) should represent the selected definition. Review existing consumers before changing a shared named calculation: a rate edit changes every dependent use, whereas the two inline columns above deliberately preserve both policies for comparison. This guide does not claim to have tested the current name-management UI, permissions, imports or mobile behavior.
Advanced: a parameterized cap with explicit boundaries
Create CappedValues, with Value and Limit in A1:B1. Enter the following pairs in A2:B6: 5,10; 10,10; 15,10; −3,10; 15,20. Enter C2:E2 and fill through row 6:
C2: =LAMBDA(x;limit;IF(x>limit;limit;x))(A2;B2)
D2: =IF(A2>B2;B2;A2)
E2: =C2-D2
C and D should be 5,10,10,−3,15, and E zero throughout. The strict greater-than comparison leaves an exact-limit value unchanged. It also preserves −3: this is an upper cap, not a lower-bound clamp or a validation rule. IF chooses the result branch inside the calculation.
Copy CappedValues as ChangedLimit and change only B4 from 10 to 12. C4/D4 become 12, and E4 remains zero. The supplied limit controls that one call; it is not a workbook-wide setting.
Recursion, errors and related functions
Zoho’s launch post documents recursion support, but the short function entry’s recursive-looking example uses an undefined function name and sends a negative x to x−1. Without a complete named definition and termination rule, it is not a reproducible recursion recipe. This guide therefore leaves recursion depth, termination and exact failure behavior unverified and uses only nonrecursive direct calls.
The reference’s shared error glossary lists invalid names, types and references. It does not establish exact errors for every argument-count mismatch, missing input, bare definition or name collision. Use the complete parameter/call pairs above before extending a formula.
LET names intermediate values within one formula; LAMBDA defines a calculation with input parameters. Zoho’s later helper announcement describes MAP, BYROW and related ways to apply such calculations to arrays. Their output-shape rules require their own checks; a successful scalar example does not establish them.
These formulas use semicolon separators, as Zoho’s examples do. Keep the inputs numeric and use the syntax displayed by the spreadsheet’s formula editor when its locale differs.