You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed a possibly incorrect behavior in the formula fields:
We need to use the formula field (or something simmilar) for calculations with input fields that are using system-defined.
The fact that input fields for formulas can have system-defined units, while the result field has none, can lead to errors in the formula if the user uses the green button to convert units (e.g. m -> mm).
Let's look at the simple example of the speed calculation v = s/t :
As long as the user does not change anything, the calculation works as intended 10 m / 2 s = 5 m/s
But if the users chlicks to change m to mm:
The result would be 1000 times greater. This would be fine, if the system was able to change the unit of the velocity to mm/s by itself, which is not yet possible, as formular-fields cannot have any system-defined units (or am I wrong?).
But without auto-units for results, the calculations is faulty.
Possible workarounds / fixes would be:
make it possible for admins to lock unit fields to a specific unit and therefor take the user the possibility to change e.g. m to mm.
don't stipulate a specific unit for the result, so that the users has to think for themself, if the result is m/s or mm/s. But that would not be a good idea and gets more complicated if hidden constants and conversion factors will be included in the formular.
Nicole also asked herself, if the value given by the use is saved, and the translation to other units is only an other "representation", or if the value is actually overwritten each time a unit conversion is performed.
In case of "only representation", that could solve the formular issues, because the calculations always uses the "saved value" and not the "shown" value (which includes the conversion factor).
The text was updated successfully, but these errors were encountered:
After reading the Docu this issue could also be a discussion about a new function, but I'm not able to convert issues to discussion.
So @cllde8 you are please free to do so.
Hi Team,
I have noticed a possibly incorrect behavior in the formula fields:We need to use the formula field (or something simmilar) for calculations with input fields that are using system-defined.
The fact that input fields for formulas can have system-defined units, while the result field has none, can lead to errors in the formula if the user uses the green button to convert units (e.g. m -> mm).
Let's look at the simple example of the speed calculation v = s/t :
As long as the user does not change anything, the calculation works as intended 10 m / 2 s = 5 m/s
But if the users chlicks to change m to mm:
The result would be 1000 times greater. This would be fine, if the system was able to change the unit of the velocity to mm/s by itself, which is not yet possible, as formular-fields cannot have any system-defined units (or am I wrong?).
But without auto-units for results, the calculations is faulty.
Possible workarounds / fixes would be:
Thanks in Advance.
Originally posted by @herrdivad in #14 (comment)
After discussion:
Nicole also asked herself, if the value given by the use is saved, and the translation to other units is only an other "representation", or if the value is actually overwritten each time a unit conversion is performed.
In case of "only representation", that could solve the formular issues, because the calculations always uses the "saved value" and not the "shown" value (which includes the conversion factor).
The text was updated successfully, but these errors were encountered: