UPPER in SoftMaker PlanMaker: Convert Text to Uppercase

Text Beginner SoftMaker PlanMaker 2026

Use UPPER in PlanMaker 2026 to turn mixed-case text into uppercase labels and codes. Exact syntax, worksheet examples, composition and troubleshooting.

Verification status: Official documentation referenced; example outcomes independently reasoned or arithmetically checked where stated. Not executed in SoftMaker PlanMaker 2026. How formula examples are checked

UPPER in SoftMaker PlanMaker 2026

Quick answer: =UPPER("PlanMaker") has the documented or independently checked expected result PLANMAKER. UPPER converts letters in a supplied text string to uppercase. It is useful for consistent identifiers, tags and display labels, while leaving the original source cell available.

What problem does this solve?

Two inventory feeds store the same product category as stock hold and STOCK HOLD; you need a consistently capitalized output column.

Use it when you want to:

  • Standardize stock status codes for reports and printed labels.
  • Create display-ready uppercase codes from mixed-case imports.
  • Produce case-normalized prefixes while retaining the original raw value.

Official syntax, argument types and defaults

=UPPER(Text)

Text (required): the text expression to convert, such as a quoted text constant, a reference to a text cell, or a text-producing formula. The published signature contains one parameter and shows no optional parameters.

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.

Reproducible worksheet: inputs and expected outputs

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.

Input cell Type this value in column A Enter this formula in column B Expected visible result
A2 pLanMaker =UPPER(A2) PLANMAKER
A3 good MORNING =UPPER(A3) GOOD MORNING
A4 aLICE kING =UPPER(A4) ALICE KING
A5 IPHONE =UPPER(A5) IPHONE
A6 CA-2048-red =UPPER(A6) CA-2048-RED
A7 Stock HOLD =UPPER(A7) STOCK HOLD
A8 customer care =UPPER(A8) CUSTOMER CARE

Enter =UPPER(A2) in B2. With pLanMaker in A2, the independently calculated expected result is PLANMAKER.

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.

Advanced formulas and practical cases

1. Convert an inventory prefix

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

Expected result: CA. LEFT extracts CA from CA-2048-red, then UPPER produces the same two uppercase letters.

2. Preserve other parts

Formula: =UPPER(A6)

Expected result: CA-2048-RED. Digits and hyphens remain as text characters; alphabetic letters change case.

3. Build an uppercase warning

Formula: =UPPER("stock hold")

Expected result: STOCK HOLD. A literal constant is valid input; the workbook source value need not be in a cell.

Common problems and troubleshooting

  • UPPER formats text content in the returned formula result; it does not set the cell font or apply a spreadsheet number format.
  • Capitalization is different from trimming excess spaces or cleaning imported nonprinting characters.
  • Mixed-language text and unusual Unicode casing are not validated by this review.
  • If output appears unchanged, check that the input already uses uppercase and that the cell contains text.
  • 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.

SoftMaker versions, platforms and Excel compatibility

  • PlanMaker 2026 (English help): documents UPPER(Text) and the core behavior described here. Source: UPPER official 2026 reference, accessed 2026-10-11.
  • PlanMaker 2024 (English help): official UPPER reference was checked for its signature and basic example; accessed 2026-10-11.
  • PlanMaker 2021: Official PlanMaker 2021, 2024, and 2026 references all publish UPPER(Text) and the same PlanMaker example. Availability in every edition/mobile build was not tested.
  • Excel: The same basic uppercase text transformation is documented for Microsoft Excel UPPER; use native testing before asserting equality for non-ASCII locales or platform/edition-specific behavior.
  • 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.

Official reference and verification

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.