ONLYOFFICE Spreadsheet Editor · References and calculation · Intermediate
Enter array formulas and check spill and compatibility behavior in ONLYOFFICE
Enter array formulas and check spill and compatibility behavior.
Documentation reviewed; native checks remain manual · Editorial standards
Quick answer
Distinguish a legacy Ctrl+Shift+Enter array, whose output range is selected in advance, from a modern dynamic array that spills into neighboring cells. ONLYOFFICE added dynamic-array support in desktop 9.3.0. Older CSE-oriented help must not be read as saying that 10.0 cannot spill results.
Scope and fixture
This task targets ONLYOFFICE Desktop Editors 10.0.0 in the English Windows/Linux interface. It gives a documented legacy-array procedure plus a separate compatibility investigation for dynamic behavior. It does not certify every Excel array formula, special spill-reference syntax, or another application’s save behavior.
In a practice XLSX workbook, enter Quantity and Price in C1:D1. Put 2, 3 and 4 in C2:C4, and 10, 20 and 30 in D2:D4. The row products are 20, 60 and 120; their sum is 200. Leave E2:E4 and G2:G4 empty. Label E1 Legacy array and G1 Dynamic check so the two experiments remain distinct.
Enter the documented legacy array
- Select the complete output range E2:E4.
- Type
=C2:C4*D2:D4in the formula bar. - Press Ctrl+Shift+Enter. The documented legacy result fills the selected range and adds braces automatically in the formula bar. Do not type the braces yourself.
- Check E2=20, E3=60 and E4=120. A correct first value alone is insufficient; all three rows must match their corresponding inputs.
- In E6, enter
=SUM(C2:C4*D2:D4)with Ctrl+Shift+Enter. The expected single-cell result is 200.
Change C3 from 3 to 5. E3 should become 100 while E2 and E4 remain 20 and 120; E6 should become 240. This checks both row-by-row alignment and aggregation without introducing another function family.
To edit a legacy multi-cell array, select its complete range and confirm the edited formula with Ctrl+Shift+Enter again. The documented warning for changing just part of a legacy array is “You cannot change part of an array.” If you want to practice removal, use a separate workbook copy, select the entire array range and delete it there. Keep the source cells separate from the output selection, and return to the intact master for the dynamic and round-trip checks below.
Investigate dynamic behavior separately
Restore C3=3. In the empty G2 area, try the same =C2:C4*D2:D4 expression with ordinary Enter on your 9.3-or-later build. Record whether it returns the expected three-row shape and the values 20, 60 and 120. This is a deliberate reader check, not a claim that this exact entry was executed during preparation.
The release documentation establishes dynamic spilling, while the rolling array help still describes Enter returning one value in its legacy explanation. Use the installed version and observed formula mode to resolve that difference; do not conclude that all array formulas require CSE on modern builds.
On a disposable duplicate, place a marker in an intended neighboring output cell before repeating the dynamic check. Observe how your build handles the obstruction, then clear the marker and repeat. Record the actual message rather than assuming another application’s error spelling, automatic overwrite behavior or special reference syntax. Never use a live report’s occupied cells for this experiment.
Check a round trip before exchanging files
Save the XLSX, reopen it in the same editor and inspect the formulas, output dimensions and values. Then, if the file must travel to another spreadsheet application, test a separate copy there and back. Repeat the C3=5 change and look for 20, 100, 120 and total 240 in the legacy fixture.
A static set of correct values can conceal a changed or lost formula. Inspect the formula bar and whether outputs still respond to inputs, not just the first opening. CSV cannot preserve this multi-cell formula behavior. For broader formula-import diagnosis, see Excel formula compatibility errors.
Sources and verification
Official documentation snapshots retrieved on 20 October 2026 support the procedures above. The worked checks are independently reasoned expectations, not a report of native application testing. Save/reopen, rendering and platform behavior remain checks for the stated installation.