Make Cell Splitter robust when input column is empty (Excel sheets with optional data)

I I process a monthly Excel. Sometimes the column has values like
20649862_21.05.2015_-31279713_7603063 which I split with Cell Splitter on _. Other times the entire column is empty. When it’s empty, Cell Splitter fails (can’t “guess” the number of output columns) and the workflow stops.

Goal: The workflow should continue even when the column is empty—ideally passing a 0-row table with the same post-split schema downstream.

Question: What’s the best practice? Thank you

@LarisaPalimaru you might want to include a case when structure that takes another path when the cell is empty or catch an error and provide an alternative

Medium: KNIME — Cases, Switches and Catching Errors
An overview of the key capabilities for workflow control

1 Like

you can do a row splitter before cell splitting on a certain character.

alternatively, splitting into a list or set should work regardless iirc

1 Like