Skip to main content
Solved

Conditional value doesn't work properly ?

  • February 15, 2017
  • 3 replies
  • 76 views
lifalin2016
Supporter
Forum|alt.badge.img+39

Hi,

 

 

I've just run into a curious problem with a conditional expression in the AttributeManager.?

 

 

I'm comnparing two dates in the "FME Date" format (%Y%m%d), setting an "expired" value to either "true" or "false" based on the conditional expression: @Value(dt1) > @Value(dt2)

 

 

But it seems like the expression is always satisfied, so my output is always "true", regardless of the values involved (and some should definitely yield "false").

 

 

As a workaround I added a Tester transformer, with the exact same expression, and that worked as expected.

 

 

Has anyone else run into this, or have any insight into why the conditional value errs ?

 

 

Cheers

Best answer by takashi

Hi @lifalin2016, you have renamed "col2" to "CreatedDate" before setting "Expired".

"col2" has been missing after renaming, and a missing attribute will be interpreted as an empty string in test clauses. I think it's the reason why "Expired" became always "true".

-- Cheers, Lars I.
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.

3 replies

lifalin2016
Supporter
Forum|alt.badge.img+39
  • lifalin2016Supporter
  • Author
  • Supporter
  • February 15, 2017

Here's a sample workspace that illustrates the problem:

condional-value-error.fmw

-- Cheers, Lars I.
takashi
Celebrity
  • takashiCelebrity
  • Best Answer
  • February 15, 2017

Hi @lifalin2016, you have renamed "col2" to "CreatedDate" before setting "Expired".

"col2" has been missing after renaming, and a missing attribute will be interpreted as an empty string in test clauses. I think it's the reason why "Expired" became always "true".

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
lifalin2016
Supporter
Forum|alt.badge.img+39
  • lifalin2016Supporter
  • Author
  • Supporter
  • February 15, 2017

Hi @lifalin2016, you have renamed "col2" to "CreatedDate" before setting "Expired".

"col2" has been missing after renaming, and a missing attribute will be interpreted as an empty string in test clauses. I think it's the reason why "Expired" became always "true".

Doh!

 

 

Grrr. Why in %¤#/& does it provide me with "col2" if it's renamed?? The value was inserted by simple point and click, so the interface is unfortunately not as user friendly as it ought to be.

 

 

Thanks Takashi.

 

-- Cheers, Lars I.

Community Stats

32,154
Posts
122,047
Replies
39,812
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.