Percentage precision not reflected with token data in automation

[Mick_Godwin]

Hi AT Community,

I'm creating an automation email within Airtable that uses percentage field data from my table.  I have set the precision to one decimal place (1.0) in the field column. 

However, when testing the automation, the preview shows that the token data percentage with 10 decimals (1.000000000), which looks ridiculous. 

Anyone know why this is happening? 

I know the workaround is a single-line entry, but I'd prefer to be able to enter the data as the percentage number, as that's how the information comes to us.

Appreciate your help!

[Greg_F · Accepted solution]

The "decimal precision" you  set on a column ,  determines only the formatting you see in Airtable. The underlying number remains the  actual complete number up to the length that the database allows. This is in case  you want  to change the decimal precision.

Looks like the second screenshot is a body of an email or similar? Best would be to format the data at destination, e.g. if you are using an external tool. In case this is e.g. email inside automations - I don't think there are any formulas to format it there.

Solution could be to have a formula field, which uses  ROUND(value, precision) .   If you use that field in Automations, it will output the number as text visible as result of the formula - meaning with decimals you need.

Let me know if that helps?

[TheTimeSavingCo · Accepted solution]

Hm, perhaps you could try adding a formula field with a `ROUND()` or other equivalent and using that for your automation instead?

[Mick_Godwin]

Great, thanks Greg.  That's the solution and good to know why it was happening.  To extend on it, I'll hide the formula field to keep the base a little cleaner.

[Mick_Godwin]

That's it.  Thanks Adam.  Appreciate it.

[Pierre-Alexand2]

Hi, I am having the same problem, but the round formula does not solve the problem for me. I even tried to converting the number to text with de concatenate formula but nothing seems to work.

[TheTimeSavingCo]

@Pierre-Alexand2 Could you share a screenshot of the relevant fields?

[Pierre-Alexand2]

Hi @TheTimeSavingCo, here is a screenshot of the 3 fields involved.

[TheTimeSavingCo]

Hm, the issue you described in your post doesn't appear to be occuring in the screenshot so I don't understand the problem.  In your screenshot the rounding seems to have worked fine?