SYIDAX / DATA GRID

Fill values PRO

Copy selected values to other cells or extend a sequence.

Fill valuesSample order data

120 rows

Loading Grid…

Options

Changes below update the Grid and code immediately.

Range selectionPROCell editingFill handlePRO

Latest result

Enter a number in Quantity and select the cell. Range selection, editing, and the fill handle are enabled in this example.

View code

Current preview

Repeat a quantity across orders or extend a sequence. First choose the source cells and target area.

Prepare the source value
Enter a number in Quantity and select the cell. Range selection, editing, and the fill handle are enabled in this example.
Drag the handle
Grab the fill handle at the selection edge and drag down within the same column.
Inspect filled values
Check target values and totals. If the fill is incorrect, click Undo.

Expected results

Values are copied or a sequence is generated according to the source range and fill mode.

Filling does not always generate a sequence. Results depend on data types and settings. Also inspect noneditable cells and validation failures.

Using this feature in your product requires the Pro runtime and a valid license.

Other properties3

Attribute / Property	Type / Default	Description
PRO enableFillHandle	`boolean`Default: undefined	ADR-022 — paint the fill handle on the last canonical range's corner (AG `enableFillHandle`).
PRO fillHandleAxes	`'both' \| 'x' \| 'y'`Default: undefined	ADR-022 — axes the drag may extend along .
PRO fillHandleMode	`'copy' \| 'series'`Default: undefined	ADR-022 — the gesture's value mode (`fillRange`'s `mode`, default copy).

Events2

Events	Detail type	Description
PRO	`SyGridFillStartEventDetail`	one per fill transaction: the ledger opening .
PRO	`SyGridFillEndEventDetail`	the status-keyed fill transaction verdict (ledger close).

Methods1

Method / Arguments	Return type	Description
PRO options: SyGridFillRangeOptions	`Promise<SyGridFillRangeReport>`	5 — API-driven fill over the sealed 57 cores (`computeFillPlan` → `computeFillValues` → `planFillTransaction`), loaded on demand as the ADR-007 'fill' chunk. ONE mint from the grid-wide counter; the sealed ledger brackets the write batch (`fillStart` → the transaction route's per-cell stream → `fillEnd`) and the plan's own per-cell entries are NEVER re-emitted — accepted writes apply through the single-authority `applyTransaction` route, so `cellValueChanged`/undo/audit/collab ride the existing emission. Structural policy: opt-in editable columns; rows without a stable id (group markers, detail panels, unloaded placeholders) are excluded as 'protected' (the identity law — id-less rows are not writable). A committed fill applies the plan's `resultingRange` to the selection . A fail-closed value plan still opens and closes the ledger (`fillEnd` status 'cancelled', the error verbatim) with zero writes.