PlanMaker ISLOGICAL: Distinguish Boolean results from numbers and labels
ISLOGICAL asks whether the referenced cell contains a logical value, TRUE or FALSE. Both values satisfy the type test. It does not ask whether the logical value is TRUE, and it does not interpret an approval label as a Boolean.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
ISLOGICAL asks whether the referenced cell contains a logical value, TRUE or FALSE. Both values satisfy the type test. It does not ask whether the logical value is TRUE, and it does not interpret an approval label as a Boolean.
Availability and verification
The PlanMaker 2026 reference, 2024 reference and 2021 reference were retrieved and compared on October 15, 2026. They document this function’s core operation. Documented by 2021 is not an original introduction date; the first introduction and any last-working-version endpoint remain unverified. The 2026/NX manual family does not establish per-build availability in FreeOffice, mobile clients or every operating system.
The examples below are vendor-supported controls and independently modeled expectations. No native PlanMaker execution, screenshot capture or workbook interchange test was performed. Keep the distinction between documentation support and observed application behavior when applying the guide to an installed version.
Syntax and argument
=ISLOGICAL(Cell)
There is one required argument and no documented optional default. Use a single-cell reference such as A2 for the worked tests. The examples deliberately keep the inspected value in a visible source cell. The formulas use English function names. The one-argument call needs no list separator; nested helper formulas below use commas, which may need adjustment for the installed locale.
Build a type-versus-value control
Create LogicalTypes with Entry, Logical_type and Text_type in A1:C1. Enter the A values below. Comparisons are used to create unambiguous Boolean results without depending on how a localized editor interprets typed words. Fill B2 =ISLOGICAL(A2) and C2 =ISTEXT(A2) through row 8.
| Row | A entry | Evaluated A | Expected B | Expected C |
|---|---|---|---|---|
| 2 | =2>1 |
TRUE | TRUE | FALSE |
| 3 | =2<1 |
FALSE | TRUE | FALSE |
| 4 | ="TRUE" |
text TRUE | FALSE | TRUE |
| 5 | ="FALSE" |
text FALSE | FALSE | TRUE |
| 6 | 1 |
number 1 | FALSE | FALSE |
| 7 | 0 |
number 0 | FALSE | FALSE |
| 8 | ="Approved" |
text Approved | FALSE | TRUE |
The FALSE result in A3 still has the logical type, so B3 is TRUE. Numbers 1 and 0 are not the same stored type as Boolean TRUE and FALSE. The quoted strings preserve their text type even when their visible spelling resembles a logical constant.
Duplicate the sheet and replace A4 with =2>1. B4 changes from FALSE to TRUE, C4 changes from TRUE to FALSE, and the visible word can remain TRUE. This control shows why appearance alone cannot validate imported approval fields.
Advanced: separate type acceptance from the decision
Create ApprovalAudit with Decision, Type_ok and Status in A1:C1. Enter =5>2, =5<2, ="TRUE", 1, and ="pending" in A2:A6. Fill B2 =ISLOGICAL(A2) and C2 below through row 6:
=IF(ISLOGICAL(A2),IF(A2,"Approved","Declined"),"Review type")
Expected B is TRUE, TRUE, FALSE, FALSE, FALSE. Expected C is Approved, Declined, Review type, Review type, Review type. The first branch checks type before the second branch interprets the Boolean decision. It does not guess whether the string TRUE or numeric 1 represents consent in this dataset.
On a copy, replace only A4 with =5<2. Its expected status becomes Declined, even though its type check now passes. That is a successful validation outcome: a valid FALSE decision should not be treated as a failed type test.
Fill D2 =IF(ISLOGICAL(A2),0,1) through D6. The initial review count =SUM(D2:D6) is 3, falling to 2 after the A4 correction. This count concerns data types, not the number of approvals.
Errors and troubleshooting
For a missing or imported value, inspect the formula bar and the actual source type. Do not convert text labels automatically without first defining the allowed labels and their meaning. This is especially important where blank, false and unknown represent different states.
The short reference defines the logical category; it does not document a complete coercion, range or error-argument matrix. This guide therefore does not promise what every malformed outer expression or specialized array will display. The composed IF formulas are independently reasoned worksheet expectations, not a native evaluation-order test.
ISTEXT tests text, ISNUMBER tests ordinary numeric values, and ISFORMULA asks whether the cell contains a formula. A formula can produce a Boolean, number or string; these are separate questions.
Verification checklist for your installation
Record the PlanMaker version/build, edition, platform, language and workbook format. Recreate the original dataset, inspect the actual formulas and then apply the specified one-cell changes on a copy. Compare the original and changed outputs, not only a screenshot of the final values. Save/reopen and cross-product import results remain separate tests; neither was performed for this guide.