The issue with your text $dates$ column is that it isn’t formatted. You have two different formats: ‘Date’ and ‘Date&Time’ in the same column. The ‘String to Date&Time’ node only works one format at a time…
Then there are few different approaches like split the data based on length()…
But the simplest way is an intermediate ‘String Manipulation’ node aiming to shape the string content into an unique text format with 19 characters. The code to be tested would be:
thank you very much for your answer.
I have implemented string manipulator node. Output after executing this node looks good, but after node string to date time input 2025-04-15T00:00:00 is shown as 2025-04-15T00:00 (seconds are missing)
Hello @Heinz
I saw it in my test. The column is now formatted as ‘Local Date Time’ type, then I think that it’s a matter of display. So you can continue with your workflow double checking, that there’s in not any bug downstream.
if you dont mind using a legacy node, the Column Expression node can solve your issue by applying a if () else () condition, checking for a “T”.
Otherwise, just do a row splitter with CONTAINS “*T*”, and then process both paths independently. for the path without T, you convert to date, and then add a Modify Time node and add 00:00:00, before appending everything together again
