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

Question

Question

8 Decimal Number in a template?

Laserfiche
Updated February 8, 2023
asked on February 7, 2023

We created a form that allows for up to 8 decimals in a number field, is there any way to transfer this to a template?

I tried a number field and it only allows up to 5 decimals and I could not find any custom formats that allow more than 1 decimal

0 0

Replies

replied on February 7, 2023 • Show version history

I just tested in my test environment, and I see the same thing.  I can make a custom format that has 8 decimals, but the Client still limits me to entering 5.  So I can make it show the 8 decimals, but I can't enter more than 5.  I can enter 12345678.12345 and make it show as 12345678.12345000, but I can't edit those last three digits.  That's somewhat annoying.

I think you might be stuck having to use a text type instead of a number type to get around this.  Bummer.

Edit to Add - yep, the documentation specifically states that the Number type is limited to five digits after the decimal.

1 0
View 1 previous reply
replied on February 7, 2023

Thanks for all the testing you do on my posts! If there is no way to do this I might see if the customer can use less decimals or maybe use a number to represent the decimals since their full integer value always seems to be 0. IE: 0.39283754

The reason they wanted it in the template is because they need to copy paste to another app and eventually WF will need to send it to the app via an API.

I never retreive data directly from Forms variables when communicating with an API, I always save to a template first. If something goes wrong with hundreds of entries it is nearly impossible to re-process them unless the data is in a template.

A single line might work too.

1 0
replied on February 7, 2023

Ah, that makes sense.  Yeah, I would agree that if it's always a zero before the decimal, storing it as an integer should be a better solution than storing as text. 

0 0
replied on February 7, 2023

If you're never going to use it as a number in conditions that depend on it being a number, i would store it as text. That would be more user-friendly to the people who have to copy it somewhere else and it would save you the headache of having to train them to "type 0, then a period, then paste".

 

0 0
replied on February 8, 2023

I am going to set it as a number field on the form, and then copy it to a text field. So when the values are typed they use a number field, but when they are copied they use a text field.

Should still be able to do any automated math by converting text to a number if needed.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...