=AND(Value1 [, Value2, Value3 ...])

Square brackets in SoftMaker’s reference are notation for optional arguments, not characters you type. The manuals do not state a maximum number of arguments in the individual AND reference, so this guide does not invent one. AND is not an exclusive-or operator; unlike OR, it requires all specified conditions to pass.

Enter the following records into a new, empty PlanMaker worksheet, with headers in row 1. Put real numeric values in B and C and actual logical values TRUE or FALSE in D (not quoted text). All formulas below refer to these exact positions.

1. Enter the entire practice table above. Make sure D2 is the boolean TRUE, not text in quotes.

2. Select an empty cell, for example G2.

3. Type:

   =AND(B2>=C2,D2=TRUE)
   

4. Expected G2: TRUE. Cable has 8 units on hand against a requirement of 5 (8>=5 is TRUE), and its approval flag is TRUE. Therefore AND(TRUE,TRUE) is TRUE.

5. Copy the expression down to G3 and G4, allowing relative references to update.

Independent sanity check: =AND(TRUE,FALSE) is expected FALSE; =AND(TRUE,TRUE) is expected TRUE, matching SoftMaker’s own reference examples.

Using only B5>=C5 and D5=TRUE would classify row 5 (Case, 0>=0) as TRUE despite no units being requested. Add a third business rule and wrap the logical result in IF:

=IF(AND(B5>=C5,C5>0,D5=TRUE),"Release","Hold")

Expected: Hold. The quantity rule C5>0 is FALSE. In a row with a genuine approved order, such as row 2, the same formula adjusted to B2, C2, and D2 is expected Release. The IF syntax and optional IfFalse argument are documented in SoftMaker’s 2026 IF manual.

To avoid an unintended empty-request release, test the business requirements individually before copying a complex condition through a live order book. The sample is illustrative and not an inventory-control system.

• =AND(B2>=C2,D2=TRUE) is about both statements; it does not choose between them. Use OR when either one is sufficient.
• A comparison D2=TRUE can be shortened to D2 when D2 is known to contain a real Boolean. The explicit form is easier to audit for mixed imported data.
• AND does not tell you which input failed. For an explanation, inspect each test separately or use an IF expression to provide a tailored message.
• A required-only version such as =AND(B2>=C2) evaluates just one logical condition; the optional syntax does not supply an invisible second condition.

1. Start with =. Without it, PlanMaker may interpret the entry as text. See SoftMaker’s formula basics.
2. Use comparisons that return logical values. For example, B2>=C2 is a test; writing "B2>=C2" is only a text string. TRUE and FALSE are logical constants, while "TRUE" and "FALSE" are text. This tutorial uses tested-by-reasoning comparisons and literal logical cells; it does not assert how arbitrary text is coerced.
3. Check row alignment and boundaries. B2>=C3 accidentally compares different orders. Verify cell addresses before assuming the formula is wrong.
4. Use English-manual argument separators as shown. The documented function syntax and examples use commas. The input/array separators shown in other manual sections can depend on regional configuration. For a different locale, use the installed PlanMaker function dialog to confirm the expected separator; no localized configuration was executed for this guide.
5. Keep calculations and business policy distinct. A logical result answers exactly the expression you wrote, not whether your workflow is sensible. Row 5 has no requested units, so a production release rule should also check C5>0.
6. Do not guess a precise error message for unchecked input. If a formula produces an error instead of TRUE/FALSE, test each referenced comparison in its own blank cell, inspect types and references, and use PlanMaker’s formula-auditing tools. Exact errors for malformed text or platform-specific coercion were not observed in native PlanMaker.

Cross-software caution: Microsoft Excel, Google Sheets and LibreOffice Calc also implement logical AND/OR/NOT patterns, but exact local separators, text-coercion, blank-cell behavior, argument ceilings, and imported workbook fidelity require testing in each application. Avoid claiming a complete compatibility guarantee from similarly named functions.

• IF guide in the owner’s 2026-10-10

• SoftMaker PlanMaker — function documentation
• SoftMaker’s 2026 IF manual
• SoftMaker’s formula basics
• PlanMaker’s formula-auditing tools
• AND — PlanMaker 2024
• AND — PlanMaker 2021

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

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