The DateFormatter was retired and the functionality has been replaced by the DateTimeConverter in FME 2017.
This was due to a major overhaul in the datetime capabilities in FME.
dateformatter.fmwtWe can see DateTimeConverter and DateTmeStamper are missing in Data Interoperability.
Safe will reach out to you so we can jointly understand your environment, then Safe and Esri will offer some options.
In the meantime the attached template can be used to import the old style DateFormatter into Workbench.
@n543
Just like David said, most of the date/time functionality is within the DateTimeConverter transformer now. Here is a blog post highlighting most of what it can do: FME2017.1: Yet Another Awesome DateTime Update
The @DateTimeFormat() function still exists within the Text Editor though. Step 6 of this exercise in the Desktop Advanced 2017 Training Manual shows how to do this.
-Liz
@n543
Just like David said, most of the date/time functionality is within the DateTimeConverter transformer now. Here is a blog post highlighting most of what it can do: FME2017.1: Yet Another Awesome DateTime Update
The @DateTimeFormat() function still exists within the Text Editor though. Step 6 of this exercise in the Desktop Advanced 2017 Training Manual shows how to do this.
-Liz
Thanks Liz, unfortunately DateTimeConverter is not available either but the @DateTimeFormat() function looks like a good alternative for now. Cheers!
Note that the DateTimeConverter (in 2017.1.1 at least) is not a complete functional replacement for DateFormatter.
The main difference (bug?) is that if there is no match on the input format, the Rejected output nulls the input attribute, making it impossible to chain these things (parsing several non-std formats) without manually copying of the original input attribute.
In DateFormatter this was the 'Set Invalid Date Attributes to: <No Action>'.