Why does Lookup (Replace) sometimes not replace all matches?

General
1

What users observe

  • Only the first matching value is replaced

  • Remaining matches stay unchanged

Why this happens

By default:

  • replaceMultipleItems = false

  • The node stops after the first successful match

This mimics Alteryx-style replace behavior.

Example

Lookup table:

  • NY → New York

  • CA → California

Input value:

  • "NY, CA"

Output (default):

  • "New York, CA"

Why this is correct

Stopping early prevents:

  • Over-aggressive replacements

  • Unexpected cascading changes

Recommendation

  • Enable Replace Multiple Items if full replacement is required