Hi, can someone please take a look at the behavior of the <Rejected> port of the DateTimeConverter and check if it's as expected:
https://knowledge.safe.com/questions/113416/different-date-formats-in-the-same-date-column.html
The behavior is described in my answer and the comments below it.
Possibly the same issue: https://knowledge.safe.com/questions/91296/datetimeconverter-rejected-port-null.html
Â
Best answer by mark2atsafe
I checked into it and there is already an issue filed with the developers, FMEENGINE-56103. So I mentioned the discussions this week, and increased the priority as best I could. Hopefully we'll see some action, since it is silly to make it null so you can't see what was wrong with it.
I don't know if the current behavior is intentional, but personally think it would be better if the transformer would output unmatched features as-is via the <Rejected> port, without replacing the datetime value with <null>.
Vote up this Idea!
https://knowledge.safe.com/content/idea/78387/improvements-to-the-datetimeconverter.html
I don't know if the current behavior is intentional, but personally think it would be better if the transformer would output unmatched features as-is via the <Rejected> port, without replacing the datetime value with <null>.
Vote up this Idea!
https://knowledge.safe.com/content/idea/78387/improvements-to-the-datetimeconverter.html
Thanks for the link @takashi, for some reason I hadn't seen it before. Upvoted.
+59I checked into it and there is already an issue filed with the developers, FMEENGINE-56103. So I mentioned the discussions this week, and increased the priority as best I could. Hopefully we'll see some action, since it is silly to make it null so you can't see what was wrong with it.
