Skip to main content
Solved

Unexpected function wrapper in DateTimeConverter

  • May 22, 2025
  • 5 replies
  • 74 views
geographix
Contributor
Forum|alt.badge.img+5

I have an attribute called “month” from an imported CSV. I’ve formatted the value to be in the format “September 1 2024”.

Now I want to convert the “month” attribute to a usable date format such as ISO YYYY-MM-DD.

If I use the dropdown to select the attribute, the value of the DateTime Attributes becomes “@Value(month)”.

When run, the workspace sends all rows to the Rejected port with fme_rejection_code. = MISSING_ATTRIBUTE_DATETIME and fme_rejection_message = Null, empty, or missing datetime was found. Enable the passthrough parameter to disable this 

However, if I manually type in “month” into Datetime Attributes:

I get the expected results:

 

Version: FME(R) 2024.2.1.0 (20241202 - Build 24801 - macosx-aarch64)

I’ve tested it on FME(R) 2025.0.2.0 (20250512 - Build 25237 - macosx-aarch64) with the same result.

Best answer by veschwab

Hi!

This seems to be a common problem (possibly a bug), you just need to make sure to choose the attribute with the arrow, not the one that starts with @Value :-)

 

Same problem here:

 

danilo_fme
matthieuv
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

5 replies

raghavendrans
Enthusiast
Forum|alt.badge.img+20

​@geographix 

Can you check if setting the parameter “Passthrough Nulls, Empties, or Missing” to “Yes” helps?

Happy FME :-) ing

Cheers

SRG

Happy FME :-) ing
veschwab
Contributor
Forum|alt.badge.img+20
  • veschwabContributor
  • Contributor
  • Best Answer
  • May 22, 2025

Hi!

This seems to be a common problem (possibly a bug), you just need to make sure to choose the attribute with the arrow, not the one that starts with @Value :-)

 

Same problem here:

 

geographix
Contributor
Forum|alt.badge.img+5
  • geographixContributor
  • Author
  • Contributor
  • May 22, 2025

​@geographix 

Can you check if setting the parameter “Passthrough Nulls, Empties, or Missing” to “Yes” helps?

Happy FME :-) ing

Cheers

SRG

The data is coming from a StatisticsCalculator in this instance with no nulls. There are only 51 records.

geographix
Contributor
Forum|alt.badge.img+5
  • geographixContributor
  • Author
  • Contributor
  • May 22, 2025

Hi!

This seems to be a common problem (possibly a bug), you just need to make sure to choose the attribute with the arrow, not the one that starts with @Value :-)

 

Same problem here:

 

Yep that is the same issue. I didn’t find that post when looking for similar issues to mine.

Thanks!

veschwab
alexbiz
Influencer
Forum|alt.badge.img+28
  • alexbizInfluencer
  • Influencer
  • May 22, 2025

I can confirm.

The "DateTime Attributes" parameter requires the name of the attribute, not its value.
With it set this way, the DateTimeConverter will look for an attribute named "September 1 2024" and try to use its value. Since your feature doesn't have an attribute with that name, you receive the error: "Null, empty, or missing datetime was found."

The DateTimeConverter shouldn't suggest selecting this value. This issue lies with the user parameter type “Attribute”, and persist in the newest version.

I’ll create an issue for safers to look at that.

Draw it, map it, shape it, fix it, share it, change it, send, translate it 🎵
veschwab

Community Stats

32,129
Posts
121,967
Replies
39,779
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.