DCOUNTA in Collabora Office: Measure Field Completeness without Losing Matching Records

• 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.

=DCOUNTA(Database; [DatabaseField]; SearchCriteria)

The field is optional only when its place is retained between separators. =DCOUNTA(A1:E8;;G1:G2) counts matching records, while =DCOUNTA(A1:E8;"Note";G1:G2) examines the selected Note cells.

The reference explicitly contrasts DCOUNTA with DCOUNT: both numeric and alphanumeric field values can contribute to DCOUNTA. This does not establish every formula-empty or error-value edge case.

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.

For Cost >=10, the selected items are A, B, F and G:

The populated notes are Ready and Done. B and G have physically empty Note cells. The zero in B’s Units cell still counts as populated; zero is a value, not an empty cell.

The Note completeness fraction is 2/4 = 0.5, or fifty percent when displayed as a percentage. It describes these four selected records, not all seven database rows.

Put Team in G4 and North in G5. This selects A, B, D, F and G. For this criteria range, the omitted-field count is 5, the Units DCOUNTA count is 4, and the Note count is 3.

The text pending in D’s Units cell contributes to the nonblank count, but it is not a numeric quantity. DCOUNT on Units gives 3 instead. A populated-field count alone therefore cannot establish numeric validity.

For the North subset, compare three separately labelled figures:

• Matching records: 5.
• Populated Units fields: 4.
• Numeric Units fields: 3.

The differences identify one physically empty Units cell and one populated nonnumeric Units cell in this controlled fixture. Keep those two issues separate rather than describing both as blank data.

The calculations use DCOUNTA with an omitted field, DCOUNTA with Units, and DCOUNT with Units. They do not infer how every possible error or empty-text formula would fit into the same reconciliation.

Restore the primary Cost >=10 criterion. Enter the text Awaiting in the previously empty Note cell E3. DCOUNTA on Note rises from 2 to 3, while the omitted-field record count remains 4.

The completeness fraction becomes 3/4 = 0.75. The Cost values did not change, so the selected record set is unchanged. This distinguishes filling a field from adding a new matching record.

Undo that edit before reusing the original fixture’s expected counts. An empty-looking result from ="" is not the same explicit test as leaving E3 physically empty; its native treatment remains unverified here.

A valid Cost >100 criterion selects no records, so both the omitted-field and selected-field counts have expected zero. A misspelled field header is instead an argument error described by the shared documentation, not evidence that no records matched.

Use DSUM when the goal is a numeric total. Counting whether data is populated and adding its numeric magnitude answer different questions.

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: DCOUNTA.
• 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.