String to Date/Time (Legacy) - bad model transposed into vers. Knime 3.7

KNIME Analytics Platform
1

Hi,
I would like to report “String to Date/Time (Legacy)” node’s bad transpose from Knime 3.4 to 3.7 version.
I have used “yyyyMMdd” pattern in 3.4 knime vers, but when I run this in 3.7 version, this pattern becomes “yyyy-MM-dd; HH: mm: ss.S” and my program end in abend.

2

Hi there!

I will check and get back to you. Sry for inconvenience.

Br,
Ivan

3

Hi there!

I have created a workflow including String to Date/Time (Legacy) node in version 3.4, exported it and then run it in the newest KNIME version and it went fine.

How did you do this transformation from KNIME 3.4 to KNIME 3.7?

Additionally I strongly advise you to use new Date&Time nodes (blog post about it is here: https://www.knime.com/blog/the-new-date-time-integration) as old ones will go from legacy to depreciated soon.

Br,
Ivan

1 Like
4