Hi @Kenyx
There isn’t really a good solution to this unless you can think of a way that as a person you’d be able to state what each of your dates represented.
For example,
-
an actual date requires a year so what date does Apr. 30 represent?
-
If you have dates both in d/m/y and m/d/y format then what date would something like 3/4/2021 represent?
Basically you will need to have some defined rules about how you are going to interpret different dates. Once you have those, we can work out how to help you implement those rules using KNIME.
If you have, for example a default year then perhaps that can be applied in the translation process.
All that said, a while ago I wrote a flexible date handing workload. On the basis that you know the order in which day month and year appear within the date string (and assuming they always all appear), it is possible to interpret a wide variety of dates in a single column. Perhaps this workflow can giving you some ideas.