Workbook Automation and Side Effects
Summary
Some U formulas perform actions—pasting, clearing, sending, launching, or controlling—rather than only returning a value.
Core Idea
Treat action formulas as explicit workflow steps with visible inputs, triggers, blocking behavior, and status outputs.
How It Works
U.EVENT converts changing state into a trigger, U.DO establishes a calculation dependency, script functions sequence steps, and supported block parameters prevent actions from running during ordinary recalculation.
Why It Matters
Excel may recalculate for many reasons. An unguarded action formula can repeat a file write, notification, publish, or remote-control command unexpectedly.
In Excel (Runline U)
Place triggers and action status cells in a dedicated control area. Keep source data and target ranges visible, and avoid hiding expensive or external side effects inside nested formulas that are difficult to audit.
Common Patterns
- Use a click value or event as the intentional trigger.
- Separate validation, action, and cleanup into distinct cells or script steps.
- Throttle actions that may be triggered by live data.
Misconceptions
- A formula returning a timestamp may still have performed an external action.
- A dependency on a volatile or RTD cell can cause repeated actions even when no user clicked anything.