Contact

Zoho Sheet SEQUENCE Function: Defaults and Reproducible Grids

Spreadsheet Advanced Zoho Sheet

Generate explicit numeric sequences, parameterized sample grids and time fractions with product-specific defaults and release evidence.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

SEQUENCE creates a numeric array with a chosen size, starting value and increment. It can generate row labels, regular sample positions or a time grid without manually entering every item. The result is a calculation that can change when its parameters change, rather than a set of permanently assigned identifiers.

Availability and evidence

Zoho’s February 6, 2020 announcement explicitly introduces SEQUENCE, together with seven other functions. The release timeline also places that update in February 2020. These establish announcement timing; neither supplies a numbered cloud build or a last functioning version.

The current SEQUENCE entry was checked on October 15, 2026. Mobile/offline parity remains unverified. The examples below are independent arithmetic expectations, not captured Zoho execution results.

Exact syntax and all three defaults

SEQUENCE(row; [column]; [first_value]; [step])

Row is the number of output rows. Column defaults to 1, first_value to 1, and step to 1. The optional arguments describe different properties: row and column control shape, while first_value and step control values. A count of five is not the final value five unless the chosen start and increment happen to make it so.

All dimensional arguments used here are positive integers. The dedicated entry does not specify coercion or exact native error behavior for zero, negative or fractional dimensions. Its visible examples show two-dimensional arrays, but no extracted result table establishes traversal order. The reproducible controls here therefore use one row or one column; no cross-product ordering rule is assumed.

Enter and troubleshoot the returned array

Zoho’s dynamic-array announcement says to enter the formula in one cell: adjacent results spill automatically, without preselecting the result range or pressing Ctrl+Shift+Enter. Leave the intended output area clear. Existing data in that area can produce #SPILL!; inspect the obstruction before moving any valuable data.

Edit the formula at its starting cell rather than treating every result cell as an independent calculation. Keep input and output areas separate. These instructions concern the documented web-service behavior; they are not a native execution or an offline-client compatibility test.

Reproducible one-column controls

Use a separate blank area for each formula so that their output ranges cannot overlap. The lists below run down a single column.

Formula Expected values, top to bottom
=SEQUENCE(5) 1,2,3,4,5
=SEQUENCE(5;1;10;2) 10,12,14,16,18
=SEQUENCE(5;1;-10;3) -10,-7,-4,-1,2
=SEQUENCE(4;1;12;0.5) 12,12.5,13,13.5
=SEQUENCE(1;1;7;2) 7

The single-value case has no second item to increment. Negative starting values and fractional steps are distinct from invalid dimensions; the official examples themselves include a negative start and a fractional step.

For a horizontal control enter =SEQUENCE(1;4;10;2) in a separate clear area. The expected one-row values are 10,12,14,16. This changes the shape, not the arithmetic progression.

Complete parameter-driven worksheet

Create SampleGrid with Count in A1, Start in B1 and Step in C1. Enter 6,2,3 in A2:C2. Leave E2:E7 clear and enter in E2:

=SEQUENCE(A2;1;B2;C2)

The expected values in E2:E7 are 2,5,8,11,14,17. The k-th item is start+(k−1)×step, so the sixth item is 2+5×3=17. The expected sum of these six values is 57.

In a copy change C2 from 3 to 4. The output becomes 2,6,10,14,18,22, with sum 72. Returning C2 to 3 and changing A2 from 6 to 4 gives only 2,5,8,11. Leave room for future expansion when the count can increase.

Advanced: sample a simple model

In a fresh clear area generate five positions using =SEQUENCE(5;1;0;0.5) in A2. The expected A2:A6 values are 0,0.5,1,1.5,2. Enter B2 =A2^2+2*A2+1 and fill through B6.

The expected model values are 1,2.25,4,6.25,9. This is the specified polynomial (x+1)² evaluated at known points. SEQUENCE chooses the positions; it does not choose a scientifically appropriate sample spacing or validate the model.

If you later increase the sequence count, the manually filled model column will not automatically gain additional formulas merely because A’s array grows. Decide separately how the downstream calculation should handle a changing result size. Zoho documents the # operator for referring to a complete spill, but this walkthrough keeps the visible five-row control explicit.

Advanced: a three-hour numeric time grid

Zoho’s author reply beneath the original announcement gives a five-row time example using an initial time cell and VALUE("3:00") as the step. To avoid locale-dependent text parsing, use the equivalent numeric day fractions in a new clear area:

=SEQUENCE(5;1;0.25;0.125)

The expected values are 0.25,0.375,0.5,0.625,0.75. With an appropriate time display they correspond to 06:00,09:00,12:00,15:00,18:00. One quarter day is six hours; one eighth day is three hours.

This is a regular spreadsheet day-fraction grid. It does not resolve a time zone, daylight-saving transition or real-world appointment duration across a clock change. Keep those requirements separate from a numeric sequence.

Errors and troubleshooting

The dedicated entry includes a shared error glossary rather than a detailed dimension-limit table. Do not treat its generic lookup-error explanation as a special SEQUENCE rule. Obstruction-related #SPILL! comes from Zoho’s separate dynamic-array documentation.

If values start correctly but end incorrectly, check whether count or final value was supplied as the first argument. If values differ by a constant amount, inspect the start; if the discrepancy grows with position, inspect the step. If old records need stable IDs, preserve assigned values separately instead of depending on a formula whose count and ordering can change.

These controls cover explicit positive dimensions and ordinary finite numeric inputs. Extreme array sizes, unsupported dimension values and native floating-point tolerances have not been tested.