Did some searching on this and couldnt come up with anything that already exists surprisingly. Over a year ago we identified that with the decimal field, it automatically truncates any trailing zeroes beyond the first place (Ex: 10.90 on the service item is changed to 10.9 after submission). This only happens with trailing zeroes. I raised it as a potential bug back then and was just now informed it’s not a bug and is considered a feature request and is not on the roadmap.
This truncation can cause questions when looking at the field as part of a service item as it’s unknown if the user missed a second digit or the value was indeed 10.90 when submitted. The ability to specify the length on the decimal field or via business rule on a service item would alleviate this while also being able to allow for further decimal points should there be a need for that. Alternatively, the creation of a field type of “currency” which mandates a length after the decimal shouldn’t be too difficult. ISO4217 (https://en.wikipedia.org/wiki/ISO_4217) shows 9 countries with more than 2 numbers after the decimal point and no countries using a single digit.
