You are viewing limited content. For full access, please sign in.

Question

Question

Error Code [LFF9304-InvalidNumberOfDecimalPlaces]

asked on August 20, 2020 Show version history

Does anyone know what is causing this? I have quite a few hidden number fields running calculations on a form that we just went live with and people are reporting getting this error with some of these fields in particular. All of them are set to have 2 decimal places, but even when there's calculations present based on empty or zero value fields, those fields should still be 0.00, as they were before I hid them.

I haven't been able to figure out why this is happening, so any advice would be much appreciated! I'd be glad to provide any more information as well, just ask. Thanks!

0 0

Replies

replied on April 30, 2024

Seeing as this is the only result when getting the error LFF9304-InvalidNumberOfDecimalPlaces, I will post my experience on resolving this...

In my case, I was using TIMEVALUE in my formula, which has a lot of decimal numbers... Since accuracy was not too important, I just rounded the result of TIMEVALUE using the ROUND formula function to the same number of decimal places in my Number field.

2 0
replied on June 25

Thank you Jay!  My problem was a date calculation that was giving a lot of decimal places to a number field with 3 decimal places max.  Modifying my calculation to add a rounding for 3 decimal places solved it.  Your post saved me a bunch of time.  Thank you!

0 0
replied on August 23, 2020

The number field is read-only? And what is the calculation settings for the number field?

0 0
replied on August 24, 2020

I'm getting the error for quite a few different fields, but the calculation was a simple =Variable to get the value selected from a drop down menu into a number field to be used with other calculations. None of the fields I'm having issues with are set to read only, they're simply hidden from the user via CSS.

Since my initial post, I think I've been able to remedy the issue simply by unchecking "Use thousandths delimiter". I have no idea why that would fix anything, but it seems to have stopped the error from occurring on those fields that I've made that change for.

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.