Enum float value behavior changed

Hi!

In our data model we have an enum with the data type integer. As you can see in the image below, the value set are floats.

Previously, the value selected by the user would correctly set as the float value from the enum, as seen in the second image.

As of now, the value is always discarding the decimal point and the output value is the rounded down int value.

Today’s behavior makes sense, as the data type is set to be an integer. However, it worked differently (and as intended) before the previous production deploy (December 10th). No related changes were made when deploying. The previous deploy before this one was from September 17th.

Is there a reason for this change in behavior?

20251212-1128-32.2500671

1 Like

Hi,

You are right, it appears that Integer Enums have unintentionally supported Float values. This behaviour changed with a code update in the platform back in October to ensure correct data type validation.