PlanMaker AGGREGATE Function: Choose a calculation and excluded cell types

=AGGREGATE(FunctionID, Options, Range1 [, Range2, ...])
=AGGREGATE(FunctionID, Options, Range1, k)

FunctionID selects the operation. Options selects which categories of cells are excluded. For operations requiring an additional selection argument, k is required rather than another input range. Supply Options explicitly: the help describes omitted Options as zero, but its displayed signature does not make the argument optional, so shortened or empty-slot forms are not assumed here.

For LARGE or SMALL, k is the desired rank, starting at 1. The help loosely calls k an integer for all six IDs 14–19, even though percentile arguments normally represent a fractional percentile. This guide does not resolve that wording by importing another product’s implementation. Its k examples use the unambiguous integer-rank LARGE/SMALL contracts.

The help’s table rendering omits the visible number beside the hidden-row-only entry, but its following paragraph explicitly identifies that behavior as Options=5. It includes filtered rows, manually hidden rows and grouped hidden rows. Hidden columns remain included. Hiding a column is not a substitute for excluding its cells from the formula.

Options 6 ignores errors but does not also promise to ignore nested totals. If a range contains both detail rows and a subtotal, selecting the wrong option can double-count the subtotal.

Enter 10, 20, 30 and 40 in A2:A5. In A6 enter =1/0 to create a genuine error value, not the text string “#DIV/0!”. Keep all rows visible for this example.

After excluding the error, the four numbers sum to 100 and have mean 25. Their descending order is 40,30,20,10, so the second largest is 30; ascending order gives second smallest 20. The stated outputs follow the documented selection rules and independent arithmetic, not a vendor-engine test.

For the same four numbers without the error row, a documented hidden-row-only sum is =AGGREGATE(9,5,A2:A5). If row 3, containing 20, is deliberately hidden, the contract predicts 80. An Options=4 sum still includes that value and predicts 100. This is a documentation-based scenario; no hidden-row interface action was tested for this guide.

Make the visibility dependency explicit in a report. A total that changes when a reader filters or hides rows is useful for a visible selection, but it may be unsuitable as an invariant grand total. Ignoring an error also does not repair its cause; audit excluded records separately.

The help explicitly states that omitting k for IDs 14–19 gives #VALUE!, with AGGREGATE(14,4,A2:A5) as the relevant pattern. Invalid FunctionID, invalid Options, all-excluded data and every coercion rule are not exhaustively specified on the short page. Avoid guessing their exact error tokens.

SUM and AVERAGE explain basic totals and means. AGGREGATE adds a specific exclusion policy; its name alone does not guarantee that calculated arrays, hidden columns or every imported value are handled like visible numeric cells.

On October 18, 2026, an XLSX containing =AGGREGATE(9,6,A2:A6) 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 first introduction release is not established by these references. 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.