01-16-2020 06:16 AM
Hello,
We track mileage reimbursement through Forms/Workflow and we take our state rate for the amount of compensation per mile. Previously the rate was $.58 per mile, which worked fine because we force users to round to the nearest whole mile when putting in their mileage. But they just changed the rate to $.575 a mile. This is causing an issue where any odd-numbered distance is creating an overall total with three decimal places, which the currency field rejects. Does anyone know of a way to get around that?
Thanks,
Rob
02-03-2020 07:37 AM
How did you get the .575 to work? do you use Currency Format for that KW? It wont allow me to use more then 2 for decimal places. The SysAdmin1700 MRG states • Decimal Places—Identifies the number of digits that follow a decimal symbol. Enter the number in the Decimal Places field. This number cannot exceed 2.
thanks,
02-03-2020 07:47 AM
We had our vendor help us out. We left the reimbursement field so that it's currency, we made the rate (.575) a floating point field, and then we did the rounding in the Unity Form in a calculated field. If you look at the list in the Expression Builder for a calculated field, there are a couple of rounding options I hadn't seen before. We used that to do the rounding so that it only allows two digits after the decimal, so the values it calculates can be copied into a currency field without any issues.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.