SUM Function in SoftMaker PlanMaker 2026: Formula, Examples & Troubleshooting

• Introduced: Documented by the PlanMaker 2010 manual; the original introduction version and date remain unknown.
• Availability: Documented in PlanMaker 2026. This identifies a documented version, not a last-working-version endpoint.
• Scope: The current entry belongs to the 2026/NX manual family; exact FreeOffice and individual mobile-build behavior is not established here.
• Checked: October 14, 2026, against the official SUM reference and historical entry. The examples were independently calculated; no native PlanMaker test was performed.

SUM(Number1 [, Number2, Number3 ...])

The current reference allows a number, range or array as an input. One leading argument is required; later arguments are optional. Commas follow the English help notation. Use the separator appropriate to your installed locale.

Stored types matter. Numbers in referenced cells are included, while text and logical values in those cells are ignored. Direct numeric-text arguments can be converted, and direct TRUE and FALSE contribute 1 and 0. The documented comparison below demonstrates why a reference and a literal are not interchangeable.

The 2010 entry prints two leading arguments, but also explicitly shows a one-range SUM example. That historical notation difference does not establish a change in runtime behavior. The formulas here follow the current entry.

Create a blank sheet named Orders, with the following data in A1:F9. Amount and Units are numeric; the other columns contain text. Keep the result cells in column H or farther right.

The complete input table is printed here, so no external practice file is needed.

H4 and H5 partition the eight rows into nonoverlapping groups. Their sum agrees with H2 because every amount is included once.

On NumericSum, enter numeric 1,2,3,4 in A1:A4. Put =SUM(A1:A4) in C1 and =SUM(1,2,3,4) in C2. Both return 10.

On a separate TypedSum sheet, put numeric 1 in A1, the formula ="2" in A2, and =TRUE() in A3. A2 produces text containing the character 2; A3 produces a logical value.

The reference result omits both the text and logical cell. The direct formula converts its explicit text-number and TRUE arguments. These cases do not establish the parsing of every imported decimal, date, currency string or invalid literal.

Return to Orders and use J2:J6:

The two blocks both include 90 and 150. SUM adds all supplied contributions, so the repeated 240 appears twice in J4. For this particular overlap, subtracting its total once reconciles the original 910. A complex workbook with several intersecting ranges needs a deliberate unique-record design rather than an assumed automatic correction.

For a signed-total check, copy Orders to SignedAmounts and replace D4 with numeric -210. H2 becomes 490: the original total decreases by 420 because +210 was replaced by -210. The row count has not changed. Negative adjustments can cancel positive values, so a small net sum does not prove that little activity occurred.

The current help also documents shortened range entry such as SUM(A5:A) and SUM(E2:2), which PlanMaker completes with additional functions for the remaining column or row. These are PlanMaker entry conveniences, not portable syntax guarantees. Keep a result outside the included range and inspect the completed formula before reusing it.

For a fixed dataset, explicit boundaries such as D2:D9 are easier to inspect. Neither a displayed total nor number formatting proves that imported cells were stored numerically.

Use SUMIF for one condition and SUMIFS for several conditions. PRODUCT multiplies included factors; SUMPRODUCT adds aligned products.

The short SUM entry does not specify every all-empty, invalid-literal, error-cell or extreme-magnitude outcome. Check stored types and exact range boundaries before assigning an unverified error token or version limitation. Cell formatting changes appearance; it does not supply a missing numeric value.