existing value changes in calculated field

[balooka]

Hi,

I have a field (field_a) with an imported value of: 0.06825066050921494

I also have a calculated field (field_b) that uses the imported field, however, if I remove all calculations and only use field_a as a 'calculation' the value in field_b, the value becomes 6825066050921494. the 0.0 is stripped of all imported values, rendering any calculation using that field useless.

Field_b result is set as a number field, indexed. 

If I change the first 0 into a 1, it updates the field but still ignores the decimal point.
Import value:
0.06825066050921494 
Changing the first 0 to 1 changes the calculated value to:
106825066050921494

I have tried to fix this by changing the decimal setting but that didn't fix it.

[comment]

Apparently your file and/or your OS is using a comma as the decimal separator, and therefore the period is ignored.

Not sure what you mean by "changing the decimal setting".

--
It seems a replay of your previous question from 7 years ago:
https://fmforums.com/topic/101702-text-field-vs-numeric-field-in-sorting-issue/#comment-462981

 

Edited March 21, 2024 by comment

[balooka]

Thanks.

 

I meant setting the field to 'decimal', instead of 'as entered'

The OS sounds like a solution, not sure if anything changed there but I'll check. I wasn't aware I could change the file's decimal separator to be honest. Will check that too.

thanks

[comment]

6 minutes ago, balooka said:

I wasn't aware I could change the file's decimal separator

You can't. You can only switch between the file's saved settings and the OS settings (with some limitations), if they are different. But you cannot change the file's saved settings. You need to create a clone of your file, open it under an OS with the desired settings, and import (or migrate) your data.

 

Edited March 21, 2024 by comment