I have many entities with DATE attributes.
When I have no value, I set them to null (NullAttributeMapper).
But DateTimeConverter generates a WARN for each null value and rejects entities, so the logfile is very big and its very slow.
I would like a parameter to ignore null values in DATE attributes (don't log them) and maybe a new output port for null values in DateTimeConverter.
+14This is definitely needed. Funnily enough the @DateTimeParse built-in function handles Null values fine. One workaround is to use an AttributeManager, and do a @DateTimeParse for every date field:
'
+8See this for info on dealing with different date formats in the same attribute.
https://knowledge.safe.com/questions/72948/convert-different-date-formats-in-same-attribute.html
What about missing or empty values?
+1Appreciate the work around suggestion. Is there a timeline on when this would be added? I'm using 2018.1 (build 18520) and the DateTimeConverter still doesn't handle nulls.
+1Appreciate the work around suggestion. Is there a timeline on when this would be added? I'm using 2018.1 (build 18520) and the DateTimeConverter still doesn't handle nulls.
+19
+14In FME 2019.0, this is now fixed by an additional parameter on the DateTimeConverter transformer.
'
'
+1@arnold_bijlsma I tried this but it outputs all null columns
Does the input attribute need to be in an FME format?
+44The transformer expects input to be in an FME format by default, but you can change that in the Input Format parameter. So you should set the input format there and then the transformer will be able to decode and convert the attribute. If the date format cannot be identified then the feature will emerge from the Rejected port and the date set to null.
+44Thanks for mentioning that. I've set the idea status to Released to reflect the new capability's release.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
