Skip to main content
Solved

Unexpected function wrapper in DateTimeConverter

geographix
Contributor
Forum|alt.badge.img+4

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:

 

View original
danilo_fme
1 person upvoted this
  • danilo_fme
    danilo_fme
Did this help you find an answer to your question?

5 replies

raghavendrans
Enthusiast
Forum|alt.badge.img+13

​@geographix 

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

Happy FME :-) ing

Cheers

SRG

veschwab
Contributor
Forum|alt.badge.img+13
  • 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+4
  • geographixContributor
  • Author
  • Contributor
  • May 22, 2025
raghavendrans wrote:

​@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+4
  • geographixContributor
  • Author
  • Contributor
  • May 22, 2025
veschwab wrote:

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
1 person upvoted this
  • veschwab
    veschwab
alexbiz
Supporter
Forum|alt.badge.img+10
  • alexbizSupporter
  • Supporter
  • 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.

veschwab
1 person upvoted this
  • veschwab
    veschwab

Reply


Helpful Members This Week

Community Stats

31,313
Posts
118,738
Replies
38,900
Members

Latest FME

Terms & ConditionsCookie settings

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
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.