ISFORMULA in Collabora Office: Formula Cells, Constant Values and Audit Flags

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

=ISFORMULA(A2)

The argument identifies the cell to inspect. With a directly entered numeric 4 in A2, the expected result is FALSE. Replace it with =2+2, and the expected result is TRUE.

Use a separate output cell so the inspection does not replace its own input. Examples use English function names and semicolons in multiargument helpers. They are independent expectations from the documented formula-cell test, not native Collabora observations.

Set up A2:A9 exactly as follows and fill =ISFORMULA(A2) down B2:B9:

For the literal-text row, the leading apostrophe is the entry marker; the intended stored text is =2+2. Do not instead enter ="=2+2", because that is itself a formula producing text and would belong to the formula category.

Formula presence remains a different property from the displayed result. An empty-looking formula and a failing formula both still contain a formula.

In C2 enter and fill down:

=IF(ISFORMULA(A2);1;0)

Expected indicators are 0, 1, 0, 1, 1, 0, 1 and 0, totaling 4. That is a count of formula definitions in this controlled range, not a count of successful calculations.

The comparison =ISNUMBER(A2) would classify the numeric result rather than its origin. ISNUMBER and ISFORMULA are useful together when an audit must distinguish a numeric constant from a calculated numeric value.

Enter quantities 2, 3 and 4 in D2:D4, with a unit amount of 10 in E2:E4. Initially put =D2*E2 in F2 and fill down. Expected results are 20, 30 and 40, and the three ISFORMULA flags are all TRUE.

Now, as a controlled comparison, replace only F3 with the numeric constant 30. The displayed values and their total 90 do not change, but the formula flags become TRUE, FALSE and TRUE.

The flag identifies that the cell no longer contains a formula. It does not prove who changed it, when it changed, or whether a constant was permitted by the actual workflow. Use a clearly documented calculation policy before labeling such a result an error.

For valid formula cells, FORMULA returns the formula text. A presentation pattern is:

=IF(ISFORMULA(F2);FORMULA(F2);"Constant or empty")

The intended selected outputs for the controlled F2:F4 example are the two retained multiplication definitions with Constant or empty for F3. This makes the difference visible beside the unchanged values.

This is a selection model based on the documented predicates and text function. It does not certify arbitrary unselected-branch evaluation behavior or every malformed reference. The underlying raw cells should remain available for inspection.

Change a valid multiplication in F2 from =D2*E2 to =D2+E2. The expected numeric result changes from 20 to 12, but ISFORMULA remains TRUE in both cases.

A formula-presence audit therefore cannot certify the operation, references, units or business rule. Compare the actual definition and use known-input controls when correctness matters. A formula can also return text, FALSE or an error without ceasing to be a formula.

The official reference establishes the formula-cell test but does not give a complete invalid-reference or array-context error matrix. These examples use actual valid single-cell references and keep native execution status explicit.

Use ISREF for the separate reference question, ISERROR for the calculated error state and FORMULA when the text of the stored expression is needed. A complete audit may need all three, rather than one broad “valid” flag.

• Collabora Office 26.04: ISFORMULA.
• Editorial testing standards.

The complete function section was reviewed. Worked controls are independently checked expectations; native execution, broader client support and unlisted edge cases remain unverified.