DPRODUCT in Collabora Office: Multiply Selected Factors and Audit Missing Inputs

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

=DPRODUCT(Database; DatabaseField; SearchCriteria)

All arguments are required. The database range includes its headers; the field identifies what to multiply after the criteria select records.

Collabora explicitly documents 0 when no records match or no numeric field values remain. Do not replace that rule with the mathematical convention that an empty product is one. An application’s no-data behavior is a separate part of its contract.

Enter this table in A1:C8. Enter the Factor numbers as actual numeric values, pending as text, and leave C8 physically empty rather than typing the displayed instruction.

Put Batch in E1 and the number 1 in E2. In a separate empty output cell use:

=DPRODUCT(A1:C8;"Factor";E1:E2)

The expected product is 1.0241, from 1.10×0.95×0.98. The text and empty cells are excluded. The result is not the arithmetic sum 3.03 of those three factors.

Field reference C1 or database index three can replace the quoted Factor header. The Batch criterion remains unchanged; filtering and selecting the measured field are separate operations.

If a model starts with a baseline quantity of 1000, multiplying it by the product gives 1024.1. The net relative change is 0.0241, or 2.41% when formatted as a percentage.

The three individual relative changes are ten percent, minus five percent and minus two percent. Adding them gives three percent, which would imply 1030 from the same baseline. Sequential multiplication instead gives 1024.1 because each factor acts on the already adjusted quantity.

These are fictional arithmetic factors, not financial projections or a claim about real-world performance. Keep the factor, baseline and interpretation labelled in the worksheet.

For Batch one, the matching-record count is 5. The populated Factor count is 4, but the numeric Factor count is 3.

Use DCOUNT with an omitted field for records, DCOUNTA on Factor for populated values, and DCOUNT on Factor for numeric values.

The product looks plausible even though two selected stages lack numeric factors. It does not prove that the process is complete. Preserve pending and the physically empty cell as separate review states rather than silently treating either as an approved factor of one.

Change E2 to the number two. The product becomes 1.08, from 1.20×0.90. A baseline of one thousand becomes 1080, an eight-percent relative increase.

In another criteria area, put Batch in E4 and >0 in E5. This selects all seven records. The combined numeric product is 1.106028, equal to 1.0241×1.08.

Combining batches only makes sense if the model actually calls for all those factors to act sequentially. The multiplication itself cannot decide whether two batches represent separate scenarios that should remain separate.

In a separate copy, add another Batch-one record with numeric Factor 1.10, and expand the database range to include it.

The Batch-one product becomes 1.12651, not 1.0241. DPRODUCT multiplies each selected numeric record; it does not deduplicate equal factor values or stage labels.

Check record IDs and expected stage counts when duplicates would be a data-quality problem. An equal-looking factor can also be a legitimate second stage, so deduplication needs a rule beyond numeric equality.

In another separate copy, change the first Batch-one factor from 1.10 to 0. The product becomes zero because an actual selected numeric factor is zero; the numeric Factor count remains three.

A criterion Batch=99 selects no records and also produces the documented DPRODUCT zero, but its numeric count is zero. Those are different states with the same result.

Likewise, a criterion selecting the text-only Stage F has no numeric factor and produces the documented zero. That does not mean pending was converted into an observed zero factor.

Criteria in one row are AND conditions; criteria on different rows are OR conditions. This tutorial’s primary numeric Batch criteria avoid text-pattern settings. For a literal Stage F check, use whole-cell matching and the exact label shown.

The shared database rules treat dates and logical values as numeric; these factor examples deliberately avoid those types. Formula-empty strings, competing errors, overflow and numeric-text conversion are not fully established here.

DPRODUCT is a multiplication operation, not a completeness validator. Keep the selected counts and original input field visible alongside its independently calculated result.

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

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