Returns TRUE when at least one supplied Boolean is TRUE, otherwise FALSE, except an error argument leads to an error. The expected return type is a Boolean TRUE/FALSE, not the words “yes” or “no”. OR checks whether any condition passes; use AND when all conditions must pass.

Use it for ticket escalation, stock checks or data-quality rules when a condition needs to be evaluated consistently across records. Use IF when a person-friendly label should appear instead of a Boolean. The distinction matters: TRUE is a logical value, while "TRUE" in quotation marks is text.

=OR(value;value;...)

Calligra’s English stable-KF6 handbook gives OR(value;value;...) (excluding the spreadsheet-cell = prefix) and lists logical inputs; it does not document a default value or a release-specific argument cap for this function. Do not copy Excel’s limit into this page without native verification. Official OR function reference.

Version and platform boundary: The pinned 26.08.2 Calligra registry contains OR in the logic module at logic.cpp line 56; the stable-KF6 function handbook independently describes it. KDE lists Calligra 26.08.2 (October 8, 2026), but this guide has not executed the function in that build, and does not establish its introduction date or support in an older edition. KDE directs Linux users to distribution packages/Flatpak and says Windows availability is being worked on. Release information · platform downloads.

Separator and locale: The English KDE examples use ; between separate function arguments; a cell range like B2:B6 uses :. Formula entry begins with =. Locale-specific punctuation, translations and numeric formatting may differ; use Insert → Function in the installed Calligra UI to confirm rather than assuming the comma-separated Excel examples work unchanged. KDE formula-entry guide.

On a blank sheet enter this table exactly, with the headers in row 1 and a numeric Priority in column B. Type the Status text without extra spaces:

Step 1. Click an unused cell, for example D2. Step 2. Enter the formula (including the leading =):

=OR(B2>=7;C2="Escalated")

Step 3. The expected result is TRUE. The priority score in B2 is 8, so the first test is TRUE even though C2 is Open rather than Escalated. This is independently checked Boolean reasoning from the shown values, not an observed Calligra calculation.

Step 4. Fill the same formula down from D2 to D6 so each reference updates to its own row. Expected results:

Exactly 4 of the five expected results are TRUE. Keep the original source columns visible so a reviewer can reproduce every comparison.

Delete the temporary D2:D6 Boolean tests, or use a separate empty result column. In D2 enter:

=IF(OR(B2>=7;C2="Escalated");"Follow up";"Routine")

Expected output for T-101: Follow up. Copy D2 down through D6: T-101, T-102, T-104 and T-105 become Follow up, while only T-103 becomes Routine. This nested use relies on the documented IF conditional syntax. When you copy the formula down, Calligra should recalculate the relative cell references; that behaviour still needs an installed-app test.

For additional auditability, place =COUNTIF(D2:D6;"Follow up") in an unused cell only if the column contains these action labels. Its expected count is 4, based on the five manually classified rows. Note: a Countif formula using a text criterion depends on the documented COUNTIF criterion syntax and should be checked in Calligra before relying on that second calculation.

The handbook specifies that an error among arguments causes an error, so do not rely on a TRUE input to hide invalid expressions. To avoid undocumented coercion, feed OR Boolean comparisons (such as B2>=7 and C2="Open"), or actual TRUE/FALSE values, rather than text placeholders such as "True" or raw imported numbers. The handbook does not establish what happens for every blank cell, mixed-type range, malformed argument, or maximum-argument boundary; those cases remain native-validation tasks.

Avoid mistaking logical conditions for a row filter. A formula in D2 only evaluates its own references. Copying it down does not filter, remove, or change underlying rows; review the result column before making operational decisions.

Additional documented sanity check: =OR(FALSE();FALSE();FALSE()) → FALSE and =OR(TRUE();FALSE()) → TRUE. These are KDE documented truth-table behaviours, not new execution claims. Official OR reference.

1. Formula is displayed as text: Make sure the entry starts with = and the cell is not being treated as a literal text value; re-enter the expression through the formula editor.
2. #VALUE! or another formula error: Check the function spelling, balanced parentheses, ; between distinct arguments, and references. KDE’s Simple Sums chapter describes #VALUE! as often indicating an expression that was not understood. It does not guarantee every logical error uses this code.
3. Unexpected TRUE/FALSE: Inspect the source values and compare each intermediate expression in a spare cell (=B2>=7 and =C2="Open", for example) before recombining them. Be alert to text with trailing spaces, numbers stored as text, and accidental quoted booleans.
4. Wrong result after filling down: Confirm that D3 references B3/C3, D4 references B4/C4, and so on; relative references move when copied.
5. Result has not refreshed: Confirm automatic recalculation is enabled or use Tools → Recalculate Sheet / Recalculate Document; KDE documents Shift+F9 / F9 shortcuts in the handbook. Current installed menus may vary.
6. Cell is too narrow: If the display becomes symbols with a red arrow, widen the cell; KDE documents that this can be a display-width issue, not necessarily a formula error. KDE troubleshooting manual.

Excel uses OR(logical1,[logical2],...) with commas in its English help and documents an Excel-specific maximum of 255 conditions. Calligra’s official handbook does not state that same maximum. Check separators and how blank or text cells are treated before importing a workbook. Do not assume imported workbook formulas are identical merely because their names match. Check Boolean handling, error propagation and separators with a small set of representative records on the destination software. Official Microsoft logical-function list is a compatibility reference, not a Calligra runtime test.

• IF guide

• Calligra Sheets — function documentation
• logic.cpp line 56
• KDE formula-entry guide
• IF conditional syntax

Verification status: Official documentation checked; example outcomes were independently reasoned or arithmetically checked where applicable. Not executed in Calligra Sheets.

• No genuine Calligra Sheets screenshots are included; this guide does not use mock application images.