DAVERAGE in Collabora Office: Use the Numeric Denominator and Combine Groups Correctly

• Introduced: the original Collabora release and launch date are not established by the reviewed sources.
• Availability: documented in Collabora Office 26.04 desktop help.
• Platform scope: online and mobile deployment support is not inferred from the desktop documentation.
• Checked: October 14, 2026. Function-specific documentation and independent controls; no native Collabora execution.

=DAVERAGE(Database; DatabaseField; SearchCriteria)

All three arguments are required. The dedicated source says nonnumeric field values are ignored. It returns #DIV/0! when no records match or no numeric field values remain among the matching records.

This differs from a zero average computed from actual observations. Do not replace every empty-subset error with zero and call it a measured mean.

Enter this database in A1:E8, including the header row. Cells marked leave empty must be physically empty; do not type those words or enter an empty-string formula. Enter pending as ordinary text.

Put the exact header Cost in G1 and the criterion >=10 in G2. The criteria range is G1:G2, including its header. It selects items A, B, F and G. Its column need not be vertically aligned with the database’s Cost column.

Use an empty output cell outside the database and criteria areas for each formula. Do not include unused rows in these criteria ranges. The database range includes all seven records, even though only four satisfy this first criterion.

With Cost >=10, use =DAVERAGE(A1:E8;"Units";G1:G2). Matching items are A, B, F and G, but only A, B and F supply numeric Units values.

The total is 10, the numeric count is 3, and the mean is 10/3. A mistaken division by all four matching records would produce 2.5, lowering the result by treating the missing value as zero.

DCOUNT with the Units field gives the correct numeric denominator for this fixture. Its omitted-field form gives the different record count.

The zero in C3 is an actual numeric observation and remains in the denominator. If you deliberately change that cell to physically empty, the same selected record set has numeric values four and six, giving mean 5.

Restore C3 to zero before the remaining examples. Changing a zero to missing data changes the meaning of the dataset; it is not a cosmetic cleanup.

For the unmodified Cost field, =DAVERAGE(A1:E8;"Cost";G1:G2) gives 14.5, from 58/4. Field choice determines both the total and the relevant denominator.

Put Team in G4 and North in G5. Put Team in H4 and South in H5. These are two separate single-column criteria ranges.

North Units values are four, zero and six, with total 10, numeric count 3 and mean 10/3. South Units values are seven and three, with total 10, count 2 and mean 5.

Use DAVERAGE with G4:G5 and H4:H5 respectively. Text pending and the empty Units cell do not become zero observations in the North mean.

A simple mean of the two group means is 25/6, approximately 4.166666667. That gives equal weight to the two groups even though they have different numeric counts.

The overall mean is instead (10+10)/(3+2) = 4. Put Cost in J1 and >0 in J2 to select all seven records in this fixture. =DAVERAGE(A1:E8;"Units";J1:J2) has expected result four.

An independent check divides DSUM on Units by DCOUNT on Units for J1:J2: twenty divided by five. Weighting each group mean by its numeric count recovers the same result.

Do not use the groups’ total record counts five and two as weights here: North has two nonnumeric or empty Units fields. The weights must match the observations used in each mean.

Change a separate criterion to Cost >100. No records match, and DAVERAGE has documented #DIV/0!. A valid North criterion with the text-only Item field also has no numeric observations and yields the same documented error.

Those are different data situations with the same error. A record count distinguishes no selected records from selected records whose chosen field is unsuitable for a numeric average.

Keep the full calculated value when combining means; the printed decimal examples are rounded. Rounding the North mean before weighting can introduce avoidable differences.

The tutorial uses ordinary numbers, explicit text and physically empty cells. The shared help separately treats dates and logical values as numeric, while a complete mixed-error or formula-empty conversion matrix is not established here. Results are independently derived expectations, not native screenshots.

The field argument selects the column to calculate after records are matched; it need not be the column used in the criteria. It can be a quoted header, a reference to its header cell, or a one-based column index within the database.

For this table, Units, C1 and index 3 identify the same field. Index three means the third database column, not an absolute worksheet-column number. The shared help says a numeric field index ignores digits after the decimal point, but the examples use integers for clarity.

Criteria in the same row are combined with AND; criteria in separate rows are combined with OR. Repeating a header lets two conditions apply to the same field. Text matching and wildcard or regular-expression behavior depend on Calc’s calculation settings. The primary numeric criterion avoids those pattern choices.

If you use literal Team criteria, enable whole-cell matching and use the exact labels shown. Do not silently treat wildcard and regular-expression modes as interchangeable. The shared database documentation also treats dates and logical values as numeric in these functions; that rule should not be replaced with another aggregation function’s type rules.

• Collabora Office 26.04: DAVERAGE.
• Shared database arguments and criteria rules.
• Editorial testing standards.

Complete function-specific and shared database documentation reviewed. Outputs are independent row-selection and arithmetic controls or explicit documented rules, not captured native results. Formulas use English names and semicolon separators.