I’m aware of the “Date&Time-based Row Filter” and this is also what makes me wonder why there is no “Date&Time-based Row Splitter”. Because usually each Filter in the nodes coming from KNIME directly has its big-splitter-sibling. Yes, you can work around it with reference row filter, but I’m pretty sure this is not a big deal Thanks
Hi @McReady ,
our plan is to upgrade the generic Row Filter and Row Splitter nodes to support date&time data types, too. In general this already works, though the UX is not ideal yet. For example, one limitation is that you cannot easily filter by the current execution time. If you filter by fixed bounds — like 2025-06-05 — it should be quite convenient already.
What do your filter criteria usually look like?
Thanks for the feedback,
nan
5 Likes
Thanks @nan for your fast reply.
Unifying the filters would be even better.
The “Current execution time” is a option I use very often. One common use case is data “valid from” or “valid to”, e.g. in ERP context for prices, rebates or VAT within automated workflows.
2 Likes