In KNIME AP:
The Value Selection Widget seems to have a bug with remember old input data.
The easiest way I’ve found to reproduce it:
Create two input tables (Table Creator will suffice). Create one column in each with the same name. Create at least one row of test data, but use different entries.
Connect Table 1 to a new Value Selection Widget, and lock the column. Optionally set to List.
Click Ok to close.
There is no need to execute this widget after closing. The bug is present even without doing that.
Connect up Table 2 (breaking the Table 1 connection).
Then execute the Value Selection Widget and then open the view for it.
As you can see, the widget has kept the list from Table 1, expects to find it, and reports it missing.
I’ve found no way to override this behavior, short of deleting the node or setting the node default to another list.
I’d instead expect that the node (especially since it has never even been ran once) to only give the items from Table 2 when first executed (and subsequently).
I did another test:
Starting with a new Value Selection Widget, I connected Table 1 to it, opened the widget config to lock the column, and then disconnected it from Table 1.
I then connected Table 2 to it and saved the workflow.
I observed this in the settings.xml - clearly showing data from BOTH tables
I then disconnected Table 2, and checked again, and it STILL had Table 1 entries in it:
All it takes for the Value Selection Widget to end up with default settings in its’ settings.xml file is for an executed node (like Table Creator) to be connected up. Disconnecting it afterwards still leaves traces of its data in an otherwise untouched Value Selection Widget.
