+6Has anyone else experienced this? I'm using FME 2022.2. If I pick an attribute from the arrow drop down menu, it inserts it in the DateTime Attributes field as @Value(CREATETIMESTAMP). When the transformer runs, it doesn't convert the value.
But if I select the attribute from the 3 dots menu, it's fine
In the 3 dots menu chooser, there are sort of two sets of the attributes....
+46It's a known issue, see here
@jakethepainter This is a common pitfall in the DataTimeConverter GUI that others have encountered. We've changed the GUI slightly in FME 2023 so that, hopefully, users are less likely to select the wrong option. The AttributeValue option is there so you can have a more dynamic DateTime conversion. Using something like @Value(dateList) allows you to dynamically set the value of dataList = date1 date2
+13I think that even in the latest version (2025.2) it is still quite confusing to choose between @value() and the attribute. As possible improvements, the error message could be more descriptive, a new section about this case could be added to the transformer help, or the GUI could be improved.
+23@jakethepainter This is a common pitfall in the DataTimeConverter GUI that others have encountered. We've changed the GUI slightly in FME 2023 so that, hopefully, users are less likely to select the wrong option. The AttributeValue option is there so you can have a more dynamic DateTime conversion. Using something like @Value(dateList) allows you to dynamically set the value of dataList = date1 date2
I’m constantly tripping over this one, wondering why the hell my datetime’s got rejected when I can see there’s good values in there, and sometimes even right after a DateTimeStamper. I would prefer the GUI be restored to simply using attribute values, since I’d never use “a more dynamic DateTime conversion”. It feels like a bug to me (FME 2025.1).
