Skip to main content
Question

Flow 2024 Parameter assignment, integers not recognized


wil
Contributor
Forum|alt.badge.img+2
  • Contributor

I am creating an Automations proces and when assigning the parameters to an integer field  get the following message: Must be a whole number. Decimals are not supported.

In the Automations first a csv is read for creating all sorts of parameters

In here there are no decimals.

In the workspace tm_data has the Type int16

In the Automations writer it is also defined as integer.

But when assigning the parameters, I receive the error. This applies for all integers I use in this.

This is a automations proces that I also build in Server 2021 and I didn't have this issue but in Flow 2024 I can't get any further because of this error.

Is there something I do wrong or is this a bug?

4 replies

wil
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • April 9, 2025

I forgot to mention, in the picture tm_datum is set as Type int16, but I changed is to int32 because the number is too big for a int16. But that did not change the problem.


kgnadt
Observer
Forum|alt.badge.img
  • Observer
  • May 15, 2025

I ran into the same problem - used to work in older FME versions, but now I get this error for almost all number parameters. Tried different int/number types but nothing works. None of the numbers ever have decimals. Would appreciate your solution if you found some, or maybe some help from FME?


wil
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • May 15, 2025

Kgnadt,

I don't have a solution but I found out that if I just assign the correct fields to the parameters, click Apply and close the configuration, even though in the Automations you will get a lot of red exclamation marks or red connections, like you see in the picture below, it won't give a problem while running the automations. If you open the configuration of the workspace, you will notice that the message in red has disappeared. The red exclamation marks or connections will stay.

 

 


kgnadt
Observer
Forum|alt.badge.img
  • Observer
  • May 15, 2025

wil, thank you for the reply! I assumed my workspaces were still working because I did not have to assign new values - always pressed “cancel” when after pressing “apply” the error in red appeared. Good to know that is works for you when assigning new values.


Reply


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