I’m building a workflow to help with some analysis.
The idea is to group SKUs by the number of totes into user specific bins. A high level grouping is shown in Table 1. I’d like to allow the user to select the specific bins in Table 1 to filter specific SKU details into Table 2. The SKU details would be the dimension and weight.
In the image below, I selected the row for Bin 1 (green) which did not update the rows in Table 2. Would someone be able to point me in the right direction please? Workflow attached further below
Thank you. It works and I’ve marked it as a solution.
I was wondering if it’s possible to do the same thing with the Table View node. It doesn’t seem there’s an output from the Table View node which could be used as a filter criteria for nodes further downstream. Does this mean Table View (Javascript) is the only option here?
Hello,
Thanks !
I’m not an expert but I think that the Knime nodes are analytics so Table view tag the selection information (see Selected column in the output) for further processing which could be filtering or grouping or pivoting anything. Unselected rows could be as important as selected ones.
Best regards,
Joel
this is also possible with the new Table, it just uses a different approach for selection.
See the attached workflow for a minimal example. We still need to rename the HiLite Row Splitter and give it an auto re-execute capability. This will make this flow much cleaner and easier to use.
The Table View seems helpful with the ability to apply color coding to multiple columns. Thanks!
The HiLite Row Splitter is very helpful, I’m not sure I understand why it’s able to filter though. I didn’t see any flow variables being sent. Can you explain that please?
sure Hiliting (soon to be called different) is a bit of a complex mechanism.
It was originally introduced a long time already in KNIME and was mostly used to see transformations to specific data points. Lets say you have a start table and do multiple transformations on it, you are able still see which row(s) resulted from this one row in your original data throughout the whole workflow. For this to work the Hiliting “flows” with the data and therefore, no additional connection is required to make it work across nodes.
Note that there are some nodes, where you have to explicitly enable the generation of this Hiliting flow (RowID node for example) and that it only works if the nodes have the same source input table.
