Good morning, I happen to recognize a few node inconsistencies amongst which [image] Collection to String The node converts one or more collection columns to a string representation. Each individual cell in the collection is converted using its 'toString()' method.… also surfaced. Whilst many nodes can be configured and execute even if not corresponding column type is present, the Collection to String can be configured but fails to execute. [Bildschirmfoto 2023-01-08 um 10.49.41] Suggestion In order to ensure workflows can proceed processing (soft fail), as data might not be consistently present or compliant, I’d like to suggest to add an option make make it default behavior to not break if corresponding collection type columns are not present. [image] Node behavior inconsistency breaks execution – mwiegand Solutions for data science: find workflows, nodes and components, and collaborate in spaces. Best Mike

Collection to String fails if no collection is present

Vernalis January 17, 2023, 4:58pm 4

Hi Mike,

This should now be fixed in the nightly build - I’m just waiting for some minor tweaks of the build job configurations for the 4.6/4.7 stable builds and it will then propagate over there too…

Steve

5 Likes