STET

Multiple formulas can apply to the same cell on a Cube, evaluated in order as the formula stack until one produces a value. STET stops that evaluation completely: no other formula in the stack is tried, even ones that would otherwise have applied further down the list. The cell's manually entered (static) value is returned immediately.

STET

STET versus CONTINUE

CONTINUE only skips the current formula and lets the engine try the next formula in the stack - which might itself go on to calculate a value for the cell. STET skips everything: the current formula and every formula after it, returning straight to the static value.

If a Cube only has a single formula applying to a cell, there's no difference between the two - with no "next formula" to try, both simply fall through to the static value.

Common pattern: a manual override that beats every formula

Use STET (rather than CONTINUE) when a user's manual entry should take precedence over the entire formula stack, not just the formula currently being evaluated - for example, a Revenue figure planned manually because of a known one-off contract, that no other formula on the Cube should be allowed to recalculate:

["Revenue", "Plan"] =
IF(
    HASSTATICVALUE(),        // has a user typed a value into this cell?
    STET,                    // yes - stop the whole stack, use that value
    ["Units"] * ["Price"]    // no - calculate from drivers
)

See Writing a Cube Formula for the fuller directional-logic-flip pattern this is usually part of.