PlanMaker SEQUENCE Function: Generate a row-first numeric sequence

=SEQUENCE(Rows [, Columns] [, StartValue] [, Step])

Columns, StartValue and Step default to 1. The prose also says omitted Rows defaults to 1, but the syntax line displays Rows as required. The examples supply Rows explicitly and do not assume that every omitted-argument form is accepted.

Rows and Columns describe output dimensions. StartValue is the first number. Step is the increment between consecutive positions. Use explicit positive integer dimensions; the short reference does not fully specify zero or fractional dimension handling.

The documented ordering is row-first: values run horizontally, then continue on the next row. For output row r and column c, the arithmetic value is:

StartValue + Step * ((r-1)*Columns + (c-1))

Choose an empty area starting at E2 and reserve E2:G3. Enter =SEQUENCE(2,3,10,2). The documented dynamic-output contract and independent calculation predict:

The sixth value uses zero-based offset 5, giving 10+2×5=20. The number of output cells is Rows×Columns=6. These checks are more precise than merely saying that the function returns “a list.”

Additional arithmetic controls are:

Negative and zero steps follow the stated increment model, but their exact application acceptance has not been independently executed here. They should not be confused with negative or zero output dimensions.

A sequence is useful for numbered positions in a report or simulation grid. For example, six columns starting at 1 with step 2 produce the arithmetic labels 1,3,5,7,9,11. These labels are generated from parameters, not inferred from the contents of neighboring records.

If records are deleted or reordered, a generated position label is not necessarily a permanent identifier. Use a stored identifier for data that must retain identity across sorting and refreshes. SEQUENCE supplies an arithmetic arrangement, not a database key policy.

For dates, a numeric increment can represent day steps only when the surrounding workbook uses an appropriate date serial and number format. A plain sequence beginning at 1 should not be labelled as a real reporting calendar without choosing a meaningful start date.

The help describes ordinary Enter entry with expansion into adjacent cells and #SPILL! if necessary destination cells are occupied. Reserve enough empty cells and review the result area when dimensions change. This is documented 2026 behavior, not an observed interface action in this guide.

The official reference suggests combining SEQUENCE with TRANSPOSE to change traversal orientation. To obtain a 2×3 grid whose numbers advance down columns, mathematically transpose a 3×2 row-first sequence: =TRANSPOSE(SEQUENCE(3,2,1,1)) gives [1,3,5; 2,4,6]. Swapping dimensions before transposition matters for a nonsquare result.

That combined expression is a documentation/mathematical extension. The separately tested 2024 TRANSPOSE workflow does not establish native execution of a nested 2026 dynamic formula.

SoftMaker’s June 9, 2026 public-beta announcement explicitly names SEQUENCE among new PlanMaker dynamic-array capabilities. The July 14, 2026 NX release announcement names it again. These establish affirmative support in those announced releases; they do not prove the earliest internal build or every prior edition’s behavior.

The help’s Excel 2021 compatibility note is about Excel, not the first PlanMaker release. No exact runtime error for every invalid dimension, text argument or arithmetic overflow is assumed from another spreadsheet.

On October 18, 2026, an XLSX containing =SEQUENCE(3) was imported into FreeOffice PlanMaker 2024 rev F1238.1005, saved as PMDX and reopened. The saved result cache was #NAME?, while the reopened live cell displayed #NULL!. The formula expression remained in PlanMaker-specific storage; the differing error displays belong to distinct stages.

This limited import/save/reopen result did not demonstrate a successful calculation. It is not a direct-entry parser test, proof of absence from every 2024 edition, or evidence about 2026 execution. The mathematical examples above remain explicitly scoped to the documented 2026 contract. No 2024 screenshot is used to illustrate a 2026 result.

Official PlanMaker 2026 function reference, checked October 18, 2026. This establishes documented support in that manual. The examples above are independent calculations or explicitly bounded documentation-based expectations; no PlanMaker 2026 native execution, screenshot or proprietary implementation inspection is claimed.

The dated announcements above are affirmative release evidence, not a claim about the earliest internal build. Absence from an older function catalogue alone does not prove runtime absence. Do not assume that installed FreeOffice 2024 implements the documented 2026 contract. Current documentation contains no retirement declaration for this function. Examples use commas; the help also shows semicolon syntax, so use the separators required by your locale.