I have a workspace where the DateTimeCalculator is failing for all records. The rejection code is always INVALID_INPUT. And yet, when I view the data in Inspector the two input fields I’m using both list as Date under Data Type. The dates look fine fine (e.g. - 20251216). It fails for any mode - Add or Subtract, Calculate Interval, etc. Any ideas why it’s failing and what I need to do to fix it? (FME Form 2025.1.0.0)
Solved
DateTimeCalculator claims invalid input for date fields
+12- Contributor
Best answer by aaron
I upgraded FME Form to 2025.2.1 (from 2025.1) and rebuilt my workspace. It works!
+62- Celebrity
Can you share a screenshot of how you have it set up? I just tried it with that date and it seems to work just fine for me
+23- Influencer
Most likely you’re running into this problem: DateTimeConverter has format of @Value(attribute) if chosen from the Attribute Value pick list vs the 3 dots window and then fails to convert value. | Community
+62- Celebrity
Most likely you’re running into this problem: DateTimeConverter has format of @Value(attribute) if chosen from the Attribute Value pick list vs the 3 dots window and then fails to convert value. | Community
No, that’s limited to the DateTimeConverter, the DateTimeCalculator doesn’t have that issue.
+23- Influencer
No, that’s limited to the DateTimeConverter, the DateTimeCalculator doesn’t have that issue.
Unless there’s a DateTimeConvertor in front of the DateTimeCalculator that does this, and it’s not noticed earlier. But you’re right, that particular problem does not affect the DateTimeCalculator itself, I missed that bit.
+12- Contributor
But I just peeked into the message under fme_expression_warnings and may have found the issue. It looks like the second value in the DateTimeCalculator is not populating. The warning reads, “Failed to evaluate expression '@DateTimeDiff(20251204,,DAYS)'. Result is set to null.” I tried testing again using the same attribute to Calculate Interval between datetimes, which should produce a value of zero (0) and FME throws the same error. That tells me it’s not the data. Bug?
+12- Contributor
- Best Answer
I upgraded FME Form to 2025.2.1 (from 2025.1) and rebuilt my workspace. It works!