Bug in string to number node

Hi, if you set up a workflow using the string to number node, and then at a later point remove one of the initial columns using column filter node (in which that column was used by string to number node for conversion), it results in the string to number node failing.

please can it be fixed such that the node still runs but just gives a warning that x column is no longer available.



Hi Simon, 

THis node still uses the old column selector dialog component.  I have logged this as an issue in our tracking system and flagged this post. 

Thanks for the report,