The simple answer is to ensure that you don’t have duplicate keys. If you’re using the cell replacer node, search keys must be unique.
Your example dictionary is:
Dictionary table Item Nr Replacement
12345 99999
12345 88888
Here, you have identical search keys being assigned to different replacements. You’re telling KNIME to look for 12345 in a cell and then replace it with 99999 and at the same time with 88888. This cannot work.
It’s worth exploring other approaches, but we’d need more information about the replacement strategy/logic and context.
Are there any other cells that make each row uniquely identifiable?
Is there a set number of replacements for each item number?
Have you successfully done this before in another software package?