Skip to main content
ReleasedFME 2023.0

Improvements to the DateTimeConverter

Related products:Transformers
  • September 13, 2018
  • 3 replies
  • 23 views
debbiatsafe
siennaatsafe
david_r
ebygomm
takashi
+7
  • debbiatsafe
    debbiatsafe
  • siennaatsafe
    siennaatsafe
  • david_r
    david_r
  • ebygomm
    ebygomm
  • takashi
    takashi
  • danilo_fme
    danilo_fme
  • jelle
    jelle
  • cwarren
    cwarren
  • juha_inkila
  • ngairedutton
  • oxyat
  • mark2atsafe
    mark2atsafe

ebygomm
Influencer

The old date time formatter allowed setting the attribute to a default value if it could not be converted. This was useful as it allowed you to set to a null value or dummy date. The datetimeformatter just passes all features with invalid dates out the rejected port, if formatting a number of attributes with dates there is no information as to which attribute has the invalid date.

3 replies

Rejected features also seem to loose the original data - it would be helpful to retain these so that further work/ manipulation on the data could be done.

LizAtSafe
Safer
Forum|alt.badge.img+16
  • Safer
  • April 5, 2025
OpenReleased

LizAtSafe
Safer
Forum|alt.badge.img+16
  • Safer
  • April 5, 2025
In FME 2023 and newer using the latest version of the DateTimeConvertor should address a few of these: the rejection message should now indicate what attribute could not be converted and the original attribute values are maintained

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings