Zoho Sheet MINA: Text-to-Zero Rules and Meaningful Minimums

• Introduced: The original introduction release and date are not established by the checked sources.
• Availability: Currently documented in Zoho Sheet’s rolling web-service help; no retirement endpoint is established.
• Scope: English-language web-service documentation. Exact mobile and offline-client parity is not established here.
• Checked: October 14, 2026, against the official MINA reference. Documentation and independent typed-value/selection calculations; no native Zoho Sheet test.

=MINA(value; [value1]; ...)

One value is required; additional values are optional, and a range can hold multiple entries. Zoho explicitly maps text to 0, TRUE to 1, and FALSE to 0. The function then returns the minimum of the evaluated values.

This is a deliberate inclusion rule. It does not validate a column, identify the record containing the minimum or distinguish a measured zero from text converted to zero. Keep the source types visible when choosing it.

Create MixedMinimum. Put Input and Manual numeric mapping in A1:B1. Enter these values:

Enter pending without enclosing quote characters. The Boolean formulas avoid relying on a text import to produce logical values. Column B is a manually entered model of the source’s rule.

Put these results in D2:D7:

The ordinary numeric minimum is 5. Adding pending introduces a mapped zero. Adding TRUE and FALSE does not lower that result further, because their mapped values are 1 and 0. D6 checks the model on ordinary numbers.

Zoho’s MIN reference documents ignoring text, which supports D7. This particular comparison uses only the numeric and text rows, without making an additional claim about MIN’s Boolean handling.

On MixedMinimum, use F2:F6:

F6 reproduces Zoho’s fully specified literal example. Negative numbers can remain below all converted text and Boolean values, so a correct negative result does not imply the extra types were ignored. F2 also shows why the minimum of positive numbers and TRUE can be 1 rather than the smallest original number.

Create PendingCosts with 8,12,pending in A2:A4. In C2 enter =MINA(A2:A4); expect 0. In C3 enter =MIN(A2:A4); expect 8.

Create MeasuredZero separately with 8,12,0 in A2:A4. The same formulas in C2:C3 both give 0. The first zero arose from a text mapping; the second is an actual numeric observation. Those meanings cannot be recovered from MINA’s single result alone.

For a completed positive-data scenario, create ResolvedCosts with 8,12,6 in A2:A4. Both =MINA(A2:A4) in C2 and =MIN(A2:A4) in C3 give 6. Keep this scenario separate rather than overwriting the pending example and continuing to expect zero.

Create AllReadyFlags. Put =TRUE() in A2 and A3, then =FALSE() in A4. Enter =MINA(A2:A3) in C2 and =MINA(A2:A4) in C3. Expected numeric results are 1 and 0.

A FALSE can lower the numeric minimum in this mapping. These numbers are not a substitute for defining the logical question or checking missing flags. The TRUE and FALSE references support the Boolean inputs; imported strings and blank-looking formulas need separate checks.

The function entry does not fully specify empty-cell handling, formula-generated empty text, every propagated error or numeric-string conversion. The examples avoid those boundaries. Number formatting alone does not prove that a digit-looking entry has a numeric stored type.

Use MIN for the documented text-ignoring comparison, MAXA for the upper evaluated extreme, and MINIFS when eligibility conditions should select the candidate records. A minimum is not a record identifier or a count of tied records. Preserve the original columns and inspect them before interpreting a surprising zero.