DMIN in Calligra Sheets: Database Criteria and Worked Examples

• Introduced: First release not established; the name is present in Calligra 2.4.0 source.
• Supported in: Calligra Sheets 26.08.2.
• Scope: Desktop Sheets, with the database function module available. No retirement endpoint is established.
• Checked: October 14, 2026. Official help and pinned source checked; examples independently calculated. Calligra was not run, so source-defined edge behavior is distinguished from displayed native results.

=DMIN(Database; Field; Criteria)

All three arguments are required. Database includes its column headers. Field is a quoted header such as "Amount", or a valid one-based column number. Criteria is another range containing header names and at least one condition row. Semicolons separate arguments in these examples. Function help; three-argument registration.

Enter this table in A1:F9, including the header row. An empty table entry means leave the cell genuinely blank. Enter 7 as a number in F6 and =TRUE() as a Boolean in F7; do not type the word “blank” into the empty cells.

Create these separate criteria blocks. Repeat a header where the table asks for it; each block includes its own header row. In two-column blocks, put the semicolon-separated entries in adjacent cells, not together in one cell.

“None” means the range ends before another condition row. Type >=75 and <=125 as criterion text. Keep the conditions outside A1:F9.

These formulas all use the Amount field. Numeric outputs are independent references, with repeating decimals rounded to twelve places.

West amounts are 75, 150 and 125, so the minimum is 75. The same minimum remains after requiring Paid status because the 75 order is Paid. The corresponding maximum changes, but that does not force the minimum to change too.

North contains 90 and a real zero, so its minimum is 0. If zero represents a legitimate free order, keep it. If zero represents missing information in the source data, correct that data policy before interpreting it as the smallest observed amount.

O1:P2 repeats the Amount header so the same row must satisfy Amount>=75 and Amount<=125. The eligible amounts are 75, 120, 90, 125 and 80. =DMIN(A1:F9;"Amount";O1:P2) returns 75.

Putting the two bounds on separate criteria rows would mean Amount>=75 or Amount<=125, a very different selection. Repeated headers on one row are useful for a closed interval. Keep the lower and upper conditions beside each other.

Conditions on the same criteria row are ANDed; different criteria rows are ORed. Repeated headers let one field satisfy two conditions. A wholly blank condition row can match every database row, so do not extend a criteria range through spare empty rows. A header-only range has no condition row and selects no data rows.

The parser silently ignores unrecognized criteria headers. A misspelled header can therefore broaden the selection, potentially to every record. Match headers carefully and test the selected IDs before relying on an aggregate. Plain words such as West in this example avoid pattern metacharacters; wildcard and regular-expression behavior depends on workbook settings. Criteria parser; condition interpretation.

An unknown target field produces #VALUE!. The evaluator considers every nonempty selected field through Calligra’s value comparisons, so use a clean numeric column and handle text or errors before computing a numerical minimum.

With no qualifying nonempty values, the source returns an empty internal value. Its display was not natively checked. Keep “no eligible value” separate from a genuine minimum of zero and count matches when the difference affects a decision.

• KDE DMIN help
• Version-pinned DMIN implementation
• Field resolution and criteria matching