Enum with Base Type Decimal

[Fabian_Weller]

When we use Enum with Base Type Decimal, and set the values to like
0.5
1.0
1.5
and so on, the Dropdown gives me
0.50
1.00
1.50

Can we change this?

[Suvrutt_Gurjar]

Hi @Fabian,

Please explore if this helps. You could set the column type as “Decimal” with decimal digits setting of 1 and valid if setting with a list such as [0.5,1.0,1.5,2.0,2.5}

Then the corresponding column shows and saves with one decimal digit.

[Fabian_Weller]

Thank you very much @Suvrutt_Gurjar.
But in my case I have to use an ENUM with Base Type Decimal.
Because I want to use not only
0.5
1.0
1.5
but also Text values like
WP
IP

This is working without any problem.

I can’t use ENUM with Base Type Text, because I need to calculate in another table with the Decimals.

[Aleksi]

One way is if you use base type as text and when you need to make some caluclations, change the value to decimal like DECIMAL([EnumColumn])

[Suvrutt_Gurjar]

Hi @Fabian,

Thank you for your updates. Got that you have text values as well…

Hi @Aleksi,

Your input as usual is practical considering @Fabian’ s requirement.

[Fabian_Weller]

Thank you both for your input. I will try that.

[Fabian_Weller]

Hi @Aleksi
I think in my case this is not working, because I’m using a reference like:
SUM([REF_ROWS_COLUMN][ENUM])

If [ENUM] is base type Text, I cannot use the expression.
And SUM(DECIMAL([REF_ROWS_COLUMN][ENUM])) ist not working.

Is there another workaround?

[Aleksi]

You would need to have a separate decimal field with a proper formula and then use that column instead of the original for the SUM().

[Fabian_Weller]

Okay, so you mean an additional VC column that converts the Text value into Decimal.
And then use this VC to calculate like:
SUM([REF_ROWS_COLUMN][ENUM_VC])

[Steve]

Fabian:

Okay, so you mean an additional VC column that converts the Text value into Decimal.

Correct.

[Fabian_Weller]

This is what I had before. But I want to get rid of all these VC columns that are consuming sync time.
That’s why I asked in my first post, if we could change the Enum Base Type Decimal to just 1 Decimal Digit.

[Aleksi]

Though you can use normal column instead of virtual.

[Fabian_Weller]

That’s a nice idea. Would you prefer normal columns instead of virtual column? What is better for sync time and performance?

[Aleksi]

In this case I would use normal column because it doesn’t need to be dynamic… like reading values from another table.

[Fabian_Weller]

Okay thank you that makes sense.

[Fabian_Weller]

I have to revise myself: ENUM with Base Type Decimal does not allow Text values. I mean, the App Editor allows. But when you select a Text value und sync it says, it’s not compatible.
So I definitely have to go the way with creating another column with AppFormula DECIMAL([EnumColumn]).

[kasun]

My coloumn type is “ENUM”. The base type is decimal. I have enabled the “Allow other values” option. But I only see two decimal places. Wants to increase it to three decimal places. Or I get errors in my calculations. How do I fix that?

[Aleksi]

Change it to Decimal type and write values into “Suggested values” option like LIST(0.123,123.123). Then you have control for decimal digits.

[kasun]

Aleksi:

LIST(0.123,123.123)

If this was not right for me. I used “valid if” to add the data in the table to the “ENUM” list. But it only shows me two decimal places. I must point out 3 decimal places in it. As you said, adding values to “Suggest value” did not work

[Koichi_Tsuji]

Try to change the data type to decimal instead of enum and set the decimal point to 3, while you keep the list expression within either valid if or suggested value