Invalid date-to-string conversion

KNIME Analytics Platform
1

Hello. Just wont to report that date with December 31 converted to string with plus 1 year (format MM/dd/yyyy only).
2027-12-31 to 12/31/2028 for example.

knime version 5.5.2

2

Hi @animebox ,

I tried, but was not able to reproduce. Could you share a small example workflow?

Just to double check, a common error is to use YYYY (week-based year) instead of the correct yyyy. The pattern in you forum post is correct, just want to really make sure this does not cause the problem.

Cheers,

nan

2 Likes
3

You must select the MM/dd/yyyy format from the drop-down list. Then the error appears. Moreover, if you manually change it to M/dd/yyyy, the error will also appear. But if you select M/dd/yyyy from the drop-down list, the error will not appear. Even more interesting, if you then manually add M and get MM/dd/yyyy, the error will not appear either. Looks like something wrong with the drop-down list of formats.

date_to_string_error.knwf (41.4 KB)

4

Glad to hear you found a workaround.

I still cannot reproduce it, but I noticed that the dropdown suggests the nonsensical format “MM/dd/YYYY” in the “United States” category. I created a ticket to remove this (internal reference UIEXT-3503).

3 Likes