PlanMaker IFEMPTY: Supply an explicit fallback for a truly empty cell

The PlanMaker 2026 reference, 2024 reference and 2021 reference were retrieved and read on October 15, 2026. These establish documented operation in those manual families, not an original introduction or a last-working-version endpoint. Both historical endpoints remain unverified. Specific FreeOffice/mobile editions and every desktop build are outside the checked scope.

The examples are documentation-backed and independently calculated or modeled. No native PlanMaker execution, screenshot, export or import test was performed. The English formulas use commas where multiple arguments are needed; localized names and separators need checking in the installed version.

Both Cell and Value are required; no optional default is documented. The vendor example uses a text fallback: =IFEMPTY(A1,"Cell is empty!"). This preserves a populated A1 value and supplies the message for an empty A1.

A fixed value after export may look correct at the time of saving but will not follow later changes to the source cell. The warning concerns future recalculation, not merely visible formatting. No actual export or destination-app test was run for this guide.

Create EmptyFallbacks with Source, Result and Blank_flag in A1:C1. Leave A2 genuinely cleared and enter the remaining values below. Fill B2 =IFEMPTY(A2,"Missing") and C2 =ISBLANK(A2) through row 7.

The numeric zero, logical FALSE and #N/A error are populated values, not genuinely empty cells. IFEMPTY is therefore not a general error-to-message replacement. These are contract-based expectations on explicit ordinary values; no native execution is claimed.

In a copy, enter numeric 0 in A2. B2 becomes 0, rather than Missing, and C2 becomes FALSE. Then clear A2 again: the message returns. This control distinguishes a real zero from absence without inferring meaning from visual formatting.

Create OptionalLabels with Item, Note and Report_note in A1:C1. Enter items A,B,C,D in A2:A5. Leave B2 cleared, enter Fragile in B3, leave B4 cleared and enter Standard in B5. Fill C2 =IFEMPTY(B2,"No note supplied") through row 5.

Expected reports are No note supplied, Fragile, No note supplied, Standard. The source note cells remain available so a placeholder in the report is not confused with something a person actually entered. In a copy, fill B4 with Keep upright: C4 changes to that text while other rows remain unchanged.

If an empty field means an incomplete required input rather than an optional note, a friendly fallback does not make the record complete. Choose the label deliberately and keep a separate completeness check. Do not automatically substitute zero into a missing price or quantity unless that meaning has been explicitly defined.

For the physically empty fixture, =IF(ISBLANK(A2),"Missing",A2) has the same independently expected result as IFEMPTY. It uses an explicit empty-cell test and a three-argument IF. That equivalence is stated only for the supplied cases; the short IFEMPTY reference does not fully specify whether formula-produced empty strings, specialized imported values or every blank-looking object are handled identically.

In particular, do not silently equate a cleared cell, a formula returning "", a space-only string and a formatted zero. Test those distinct inputs in the target build if they matter to the workbook. The guide intentionally does not include the ambiguous cases as proven IFEMPTY results.

On a copy of OptionalLabels, replace C2 with the fixed text No note supplied, then enter Urgent in B2. The fixed C2 stays unchanged, whereas a live IFEMPTY formula is expected to show Urgent. This is a controlled dependency-loss simulation, not evidence that an exporter was executed.

ISBLANK tests emptiness, IFERROR handles errors, and IFNA targets #N/A. These are different predicates and fallback policies. Preserve the unsupported-function export warning when choosing a portable workbook design.

Record the exact product/build, edition, platform, language and workbook format. Recreate the original cells, inspect the actual formulas and apply each changed-input control on a separate copy. Verify saved-file recalculation and destination compatibility independently; neither follows merely from a matching displayed result.