Contact

ISLOGICAL in WPS Spreadsheet: Distinguish Boolean Type from a True Condition

Information Intermediate WPS Spreadsheet

Check actual TRUE and FALSE values in WPS Spreadsheet, separate Boolean results from text or numeric flags and count typed logical records explicitly.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

Quick answer: ISLOGICAL returns TRUE when its argument is a logical value. Both =ISLOGICAL(TRUE()) and =ISLOGICAL(FALSE()) have expected result TRUE. The function tests the value’s type, not whether that value is true.

Availability and version history

  • Introduced: documented by 2019-05-14 in WPS material; the first release is not established.
  • Availability: current WPS Windows documentation identifies the function as built-in; the dedicated historical lesson has a blank edition field.
  • Scope: exact supported builds and other WPS clients remain unverified.
  • Checked: October 14, 2026. Documentation and independent examples; no native WPS execution.

Syntax and the type distinction

=ISLOGICAL(value)

The dedicated WPS lesson describes TRUE and FALSE as logical values and explicitly contrasts them with the number one, which is not logical. Its shared IS-function reference also explains that these tests do not convert an argument merely to make it fit another type.

The old walkthrough misspells TRUE as TURE in some prose. Its meaning is the Boolean TRUE already used in the shared formal description, not another supported spelling or alias. Current WPS Windows documentation explicitly defines the tested logical values as TRUE or FALSE.

Example 1: make each input type reproducible

Enter the formulas below in A2:A9. Formula-generated quoted strings keep the text cases distinct from typed Boolean values. In B2 enter =ISLOGICAL(A2) and fill down.

Cell Enter in A Expected value category B, logical type?
A2 =TRUE() Logical TRUE TRUE
A3 =FALSE() Logical FALSE TRUE
A4 =1 Number one FALSE
A5 =0 Number zero FALSE
A6 ="TRUE" Text TRUE FALSE
A7 ="FALSE" Text FALSE FALSE
A8 =2>1 Logical TRUE TRUE
A9 =2<1 Logical FALSE TRUE

A2 and A6 may look similar on screen, but they supply different types. The same distinction separates A3 and A7. The visible letters alone do not establish a logical value.

The fourth TRUE in B belongs to a comparison that evaluates to FALSE in A9. That is expected: the comparison still produced a logical result.

Example 2: compare type-specific checks

For A4, =ISNUMBER(A4) has expected TRUE and ISLOGICAL has expected FALSE. For A6, =ISTEXT(A6) has expected TRUE and ISLOGICAL has expected FALSE.

ISNUMBER and ISTEXT answer different questions. A number can be used by some formulas as a flag without becoming a Boolean-typed value for ISLOGICAL.

Likewise, TRUE and FALSE are different states of the same logical type. Use an actual condition when the question is whether a rule passed; use ISLOGICAL when the question is whether its stored result has the expected type.

Advanced example: count logical records explicitly

Put =IF(B2,1,0) in C2 and fill through C9. The eight numeric flags are 1, 1, 0, 0, 0, 0, 1 and 1.

=SUM(C2:C9) gives 4 logical-typed records. This count includes both TRUE and FALSE values. It is a count of a type, not a count of successful conditions.

The IF branches explicitly produce numbers before SUM is used. This avoids relying on a separate implicit Boolean-to-number aggregation rule. Every B cell is itself a well-defined Boolean type-test result in this fixture.

Changing A3 from =FALSE() to =TRUE() changes its state but leaves the logical-record count at four. Changing A3 to ="FALSE" changes its type and reduces the count to three.

Advanced example: preserve Boolean type in a result formula

Suppose a numeric score in E2 is 72, with threshold 60 in F2. Compare:

=E2>=F2
=IF(E2>=F2,TRUE(),FALSE())
=IF(E2>=F2,"TRUE","FALSE")

The first two have expected logical TRUE results, while the third returns text TRUE. Applying ISLOGICAL to those results gives TRUE, TRUE and FALSE.

Change the score to 55. The first two now produce logical FALSE and the third text FALSE, but their ISLOGICAL classifications remain TRUE, TRUE and FALSE. The type test does not confuse a failed threshold condition with a wrong result type.

TRUE and FALSE make the intended Boolean constants explicit. Quoted words create text instead.

Errors, blank values and scope

The examples use explicit logical, numeric and text values. They do not infer every behavior for a blank reference, existing error, array or imported application-specific value. A separate error test is appropriate when the question is whether a formula failed.

The historical source’s blank edition field is recorded in the availability section; the earlier shared Windows lesson and current Windows identity evidence have their own scope. Neither establishes a minimum current build or a universal cross-client support range. Worked outputs are independently modeled, not native WPS captures.

References and verification

Complete function-specific sources reviewed. Expected results are independently derived controls, not native application captures. Formulas use English names and comma separators; check the installed locale.