RIGHT in SoftMaker PlanMaker: Extract Trailing Text

=RIGHT(TextString [, n])

Brackets indicate optional syntax, not literal characters. The 2021 manual labels the first input Text, whereas the 2024 and 2026 manuals say TextString. Both versions use the RIGHT("peanut",3) → nut example; this label change is not evidence of different runtime behavior. No PlanMaker-specific error type is asserted here for invalid or negative counts because the official RIGHT reference does not describe one.

On a new, empty worksheet, type the following entries into the indicated cells. Treat codes as text, including their leading zeroes. These deliberately use only ordinary ASCII letters, hyphens and digits so that Unicode counting differences are outside the examples.

For row 1, enter the header words without the Markdown bold markers. Each item code is 11 characters: two letters, a hyphen, four digits, another hyphen, and three letters. Enter formulas in empty cells, such as E2 onward, so the example data is never overwritten.

1. Confirm column A contains the five exact text codes printed above.
2. Enter =RIGHT(A2,3) in E2.
3. Expected E2: RED because the final three characters are R, E and D.
4. Fill down through E6 using relative references.

=RIGHT(A2) should instead give the expected D, because the optional count defaults to 1. The official reference confirms the same behavior with RIGHT("peanut") → t.

Use =RIGHT(A2,8) to include the four-digit serial number, separator, and three-letter colour suffix. Expected result: 2048-RED. Asking for three characters gives only RED, while asking for eight gives all characters from position 4 onward. LEFT uses the opposite end of the string.

=IF(RIGHT(A2,3)="RED","Red variant","Another variant")

To check both ends of a code without assuming every middle section is valid, use:

=IF(AND(LEFT(A2,2)="US",RIGHT(A2,3)="RED"),"US red","Other")

Expected A2: Other; expected A5: US red. This checks only those two portions, not the interior serial number. For validation rules, you may also need MID and LEN.

• Incorrect count: =RIGHT(A2,4) gives -RED, not RED, because the hyphen is the fourth character from the end.
• Confusing last character with last word: RIGHT counts characters, not words or comma-delimited fields; a three-character suffix is just a text convention in this dataset.
• Preserving leading zeros elsewhere in the code: RIGHT returns the tail of the text code. For the interior 0052, use MID(A3,4,4) instead and preserve the result as text.
• Trailing spaces: spaces are part of a text string. An extra space after RED changes what RIGHT(A2,3) selects; inspect source content before applying fixes.
• Overclaiming edge cases: the official reference documents the default n=1 but does not establish negative/fractional argument behavior for every platform. Do not assume Excel’s exact error codes hold in PlanMaker without running PlanMaker.
• Formula entered as text: begin with =, enter without Markdown backticks, and confirm in the cell. Formula basics.

• Begin worksheet formulas with =. The PlanMaker 2026 formula basics explicitly requires it.
• Arguments in these English-language SoftMaker references use commas. If your installed locale expects different separators or displays a localized function name, use Formula → Function to verify the spelling and separator; no non-English installation was tested here. Quotation marks around literal strings are ordinary formula syntax.
• SoftMaker’s English PlanMaker 2021, 2024 and 2026 manuals document this function. That is evidence of documentation in those editions, not proof of a first-introduced version or identical behavior on FreeOffice, NX, Android, iOS or every operating-system build. PlanMaker’s general 2026 documentation names Windows, macOS, Linux, Android and iOS, but no platform-specific execution was performed.
• A formula in this guide may be a documentation-supported example or an independently calculated expected output; neither is an observed result from native PlanMaker. The specific example tables below are computed from the printed input strings.

These formula names have the same basic text-extraction/counting purpose in Microsoft Excel. For the ordinary ASCII examples in this guide, Excel’s published formulas imply the same outputs. However, do not assume every locale, date/number conversion, Unicode character (especially emoji or surrogate pairs), file-format conversion, or Excel Compatibility Version 2 case behaves identically in PlanMaker. Microsoft’s current documentation describes newer Unicode behavior for some Excel functions; the SoftMaker individual references do not document an equivalent switch. Workbook transfers and target-platform behavior therefore require testing.

The same terminology in LibreOffice/OpenOffice/Google Sheets is not independent proof of perfect compatibility. Check the target application’s functions, formula separators, text encoding and worksheet locale when migrating.

• SoftMaker PlanMaker — function documentation
• SoftMaker’s 2026 IF reference
• Formula basics
• RIGHT — PlanMaker 2021
• 2024
• LEFT
• MID

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.