LOWER in SoftMaker PlanMaker: Convert Text to Lowercase

You receive customer or stock labels written with inconsistent capitalization, so exact case no longer matters for display or downstream grouping.

Use it when you want to:

• Normalize imported department names before comparing or reviewing them.
• Make search keys display consistently while retaining source data in another column.
• Prepare uniform lowercase text fragments in longer formulas.

=LOWER(Text string)

Text string (required): a quoted text literal, a cell reference containing text, or an expression that evaluates to text. No second argument or optional argument is documented.

Required/optional arguments: one required text argument; none optional in the official 2026 signature. Default values: none. Text literals must be placed in double quotes; plain A1-style references refer to cells. Outputs are text, not a change to the input cell.

Function spelling: function names appear in English in the cited English-language documentation. The examples use formula syntax shown there. Because these three functions have only one argument, comma-versus-semicolon function-argument separators do not arise in their standalone formulas; formula names, locale details and separators for other functions may depend on the installed language/region and must be checked in your PlanMaker edition.

Create a new PlanMaker workbook. Type Source text in A1 and Formula result in B1. Enter the following values in the specified A-column cells, then enter the B-column formulas. Sample text has been chosen to avoid unverified accent/Unicode and punctuation-based word-boundary cases.

Entering =LOWER(A2) in B2 yields the expected text planmaker from pLanMaker in A2. The formula does not modify the source cell.

Reproduce: after filling the A cells, enter the formula in the matching B cell and press Enter. If you copy a formula down, verify its automatically adjusted relative cell reference. Inputs can also be given directly as quoted text.

Validation disclosure: results above are expected, not observed within PlanMaker. Independent calculation used ASCII string operations in Python; it is neither the PlanMaker calculation engine nor a claim of native testing. Vendor example behavior was checked against official documentation. Exact installed-version behavior still needs owner testing.

1. Create a standardized prefix

Formula: =LOWER(LEFT(A6,2))

Expected result: ca. The nested LEFT extracts the first two characters of CA-2048-red and LOWER changes their case; LEFT behavior follows the previously documented PlanMaker LEFT reference.

2. Normalize then label

Formula: ="status: "&LOWER(A7)

Expected result: status: stock hold. The formula joins a fixed label with the lowercase version of Stock HOLD; Excel-style text concatenation using & needs native PlanMaker execution before release.

3. Avoid changing numbers

Formula: =LOWER(A5)

Expected result: iphone. LOWER changes text case, not the underlying identifier or values in the source cell.

• The letters in the referenced cell remain unchanged; LOWER returns its result in the formula cell.
• LOWER is not a whitespace-cleaning or spelling-correction function; spaces, punctuation and typos are separate problems.
• When a formula displays as raw text, inspect whether the cell is text-formatted or the formula begins with an apostrophe; verify the issue in the installed edition.
• If the software displays a syntax or name error, check the function name, leading =, matching parentheses and quotation marks. No specific error-code result is asserted without native execution.
• If a referenced input already contains a spreadsheet error, the result should not be treated as independently validated here; reproduce this edge case in the actual version before documenting a definite error outcome.
• If text changes visually but your original cell looks the same, remember formulas return into their own cells. Review carefully before using paste-as-values to replace source data.

• PlanMaker 2026 (English help): documents LOWER(Text string) and the core behavior described here. Source: LOWER official 2026 reference, accessed 2026-10-11.
• PlanMaker 2024 (English help): official LOWER reference was checked for its signature and basic example; accessed 2026-10-11.
• PlanMaker 2021: The 2021 LOWER detail page was not accessible in this review; do not infer release introduction or exact 2021 behavior from 2024/2026.
• Excel: Microsoft Excel documents LOWER for the same essential ASCII-text transformation. Do not assume identical Unicode, locale or error coercion edge cases without execution in both applications.
• Platforms/editions: This research concerns the 2026 desktop English help reference; availability in Windows, macOS, Linux, Android/iOS or particular product editions was not tested. Official documentation membership is not proof of runtime parity in every platform.
• File formats: Do not assume behavior on conversion to legacy formats (.xls), XLSX interoperability or formula-preservation for every edge case; those scenarios require actual save/reopen comparison.

• LOWER — convert letters to lowercase (official 2026 SoftMaker help; checked 2026-10-11).
• UPPER — convert letters to uppercase (official 2026 SoftMaker help; checked 2026-10-11).
• PROPER — capitalize the beginning of words (official 2026 SoftMaker help; checked 2026-10-11).

• SoftMaker PlanMaker — function documentation
• LOWER reference
• UPPER — convert letters to uppercase
• PROPER — capitalize the beginning of words

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.