Skip to main content
Solved

Keep the fme_time Schema When Using Conditional Values


krystalp
Contributor
Forum|alt.badge.img+3

I have 3 datasets that are fme_time schema type and I want to use the AttributeManager Conditional Value to set if/else statements depending on which time values are missing. When I do this, the resulting attribute type is fme_varchar and not fme_time. If I create a new attribute and point to just any one of these attributes, the new resulting attribute is still fme_time. So it appears the conditional value setting is changing it and I can't figure out how to change it back to a time. I have tried parsing, formatting, casting and nothing changes the varchar back to time. Are there any ideas to fix this?Condition Statement and attributes 

Showing original attribute is fme_time 

Showing resulting conditional result is fme_varchar 

Showing resulting simple field creation from time field is still fme_time 

Best answer by dustin

I don't have answer for you in any of the official releases of FME, but in the beta version of FME2023 (build 23215), I can confirm that the new 'type' parameter in the AttributeCreator and AttributeManager does in fact change the type to fme_time.imageimage

View original
Did this help you find an answer to your question?

4 replies

dustin
Influencer
Forum|alt.badge.img+30
  • Influencer
  • Best Answer
  • January 27, 2023

I don't have answer for you in any of the official releases of FME, but in the beta version of FME2023 (build 23215), I can confirm that the new 'type' parameter in the AttributeCreator and AttributeManager does in fact change the type to fme_time.imageimage


krystalp
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • January 27, 2023
dustin wrote:

I don't have answer for you in any of the official releases of FME, but in the beta version of FME2023 (build 23215), I can confirm that the new 'type' parameter in the AttributeCreator and AttributeManager does in fact change the type to fme_time.imageimage

Thanks for checking that. Are you able to test with it being in a conditional value? That’s where I was having issues.


dustin
Influencer
Forum|alt.badge.img+30
  • Influencer
  • January 27, 2023
krystalp wrote:

Thanks for checking that. Are you able to test with it being in a conditional value? That’s where I was having issues.

Yes, confirmed that it still works as expected with a conditional statement.


krystalp
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • January 27, 2023
krystalp wrote:

Thanks for checking that. Are you able to test with it being in a conditional value? That’s where I was having issues.

Great. Looking forward to 2023 coming out. :)


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