PlanMaker FALSE: Logical Flags, Types and Review Rules
Return logical FALSE in PlanMaker with complete type checks, review flags and neutral OR conditions without guessing import behavior.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: =FALSE() returns PlanMaker’s logical value FALSE. It takes no arguments. It can serve as an explicit disabled flag or a neutral condition in OR, but it does not test whether another cell is false.
Availability and version history
- Introduced: Documented by the PlanMaker 2010 manual; the original introduction release and date remain unknown.
- Availability: Documented in PlanMaker 2026. This identifies a documented version, not a last-working-version endpoint.
- Scope: The current entry belongs to the 2026/NX manual family; exact FreeOffice and individual mobile-build behavior is not established here.
- Checked: October 14, 2026, against the official FALSE reference and historical entry. The examples were independently calculated; no native PlanMaker test was performed.
Syntax and distinct stored types
=FALSE()
Do not supply an argument inside the parentheses. Logical FALSE, numeric zero, the text string “FALSE” and a genuinely empty cell are different types or states. Similar displayed values do not establish identical behavior in other functions.
The official entry establishes the function result, not every importer’s conversion of the letters FALSE. The examples therefore use FALSE() explicitly for logical cells.
Check the type rather than the display
Create FalseTypes with Input formula, Logical type and Text type in A1:C1. Enter the A formulas below. Put =ISLOGICAL(A2) in B2 and =ISTEXT(A2) in C2, then fill B2:C2 through row 6.
| Row | Formula in A | Expected B | Expected C |
|---|---|---|---|
| 2 | =FALSE() |
TRUE | FALSE |
| 3 | ="FALSE" |
FALSE | TRUE |
| 4 | =0 |
FALSE | FALSE |
| 5 | =1>2 |
TRUE | FALSE |
| 6 | =TRUE() |
TRUE | FALSE |
ISLOGICAL accepts either logical value as the type being tested. ISTEXT recognizes the string returned in A3. A comparison can return logical FALSE without calling FALSE() itself, as A5 demonstrates.
In E2 enter =NOT(FALSE()); expect TRUE. In E3 enter =IF(FALSE(),"Selected","Not selected"); expect Not selected. Both branches of IF are explicitly supplied, so this example does not rely on an undocumented omitted-result default.
A global review flag alongside ordinary checks
Create ReportChecks with Report, Complete, Differences and Review required in A1:D1. Enter:
| Row | A | B: Complete | C: Differences |
|---|---|---|---|
| 2 | R1 | Yes | 0 |
| 3 | R2 | No | 0 |
| 4 | R3 | Yes | 2 |
| 5 | R4 | No | 3 |
Put Review all in G2 and =FALSE() in H2. In D2 enter =OR(B2<>"Yes",C2>0,$H$2) and fill through D5. Expect FALSE,TRUE,TRUE,TRUE.
FALSE contributes no additional reason to review these valid logical conditions. Change H2 to =TRUE(); all four results become TRUE because the global flag itself now requests review. The input records have not changed. Restore H2 to FALSE() afterward.
In E2 enter =IF(D2,"Review","No flagged issue") and fill through E5. After restoration, expect No flagged issue,Review,Review,Review. The first label means these specific tests found no issue; it is not a guarantee of overall report correctness.
Disable an optional check without disabling a mandatory one
Add Check differences in G3 and =TRUE() in H3. In F2 enter the following and fill through F5:
=OR(B2<>"Yes",IF($H$3,C2>0,FALSE()))
With H3 TRUE, expect FALSE,TRUE,TRUE,TRUE. With H3 FALSE, expect FALSE,TRUE,FALSE,TRUE. R3 changes because its only reason for review was the now-disabled difference check. R2 and R4 remain flagged because the completion check is still active.
Only use this pattern when that condition is genuinely optional for the worksheet’s purpose. A required check should not be disabled just to remove a warning. Restore H3 to TRUE after the comparison.
Neutral in OR does not mean neutral everywhere
On FalseControls, enter =FALSE() in A2 and =TRUE() in A3. Put =OR(A2,FALSE()) in B2, =AND(A2,FALSE()) in C2 and =NOT(A2) in D2; fill B2:D2 through row 3.
| Row | Expected B | Expected C | Expected D |
|---|---|---|---|
| 2 | FALSE | FALSE | TRUE |
| 3 | TRUE | FALSE | FALSE |
OR(x,FALSE) preserves a valid logical x, while AND(x,FALSE) returns FALSE. These rules do not promise lazy evaluation or that an unrelated error is hidden.
The short FALSE entry does not establish exact malformed-call errors, imported-type conversions or client/export parity. Keep those questions separate from the demonstrated logical constant.
TRUE supplies the opposite value. OR, AND, NOT and IF support the explicitly defined rules above. The comma-separated examples follow the English help syntax.