# How to get numeric entry fields to display whole numbers as percents

**URL:** <https://forum.inductiveautomation.com/t/how-to-get-numeric-entry-fields-to-display-whole-numbers-as-percents/103969>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 20, 2025, 5:52pm UTC](https://forum.inductiveautomation.com/t/how-to-get-numeric-entry-fields-to-display-whole-numbers-as-percents/103969 "2025-03-20T17:52:59Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Noah\_Gilgo](https://avatars.discourse-cdn.com/v4/letter/n/c89c15/32.png) [@Noah\_Gilgo](https://forum.inductiveautomation.com/u/Noah_Gilgo)\
**Post date:** [March 20, 2025, 5:52pm UTC](https://forum.inductiveautomation.com/t/how-to-get-numeric-entry-fields-to-display-whole-numbers-as-percents/103969/1 "2025-03-20T17:52:59Z")

</div>

My client wants certain numeric entry components for inputting percentages between 0-100%. I want the ability to input a whole number like 53 into the field and have it formatted to render as '53%'.

I tried entering `#'%'` into the `format` field on the numeric entry component, but no matter what I do, the component always multiplies the values I enter by 100 before displaying them as percents. (eg. 53 -\> 5300%)

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [March 20, 2025, 6:08pm UTC](https://forum.inductiveautomation.com/t/how-to-get-numeric-entry-fields-to-display-whole-numbers-as-percents/103969/2 "2025-03-20T18:08:17Z")

</div>

Put the % in a label to the right of the numeric entry field - same as you would with units (kg, s, m/s, etc.).

---

<div class="post-metadata">

**Author:** ![Noah\_Gilgo](https://avatars.discourse-cdn.com/v4/letter/n/c89c15/32.png) [@Noah\_Gilgo](https://forum.inductiveautomation.com/u/Noah_Gilgo)\
**Post date:** [March 20, 2025, 6:37pm UTC](https://forum.inductiveautomation.com/t/how-to-get-numeric-entry-fields-to-display-whole-numbers-as-percents/103969/3 "2025-03-20T18:37:38Z")

</div>

Is it not possible to format numeric entry fields in the way that I described without labels or additional components?

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [March 20, 2025, 6:43pm UTC](https://forum.inductiveautomation.com/t/how-to-get-numeric-entry-fields-to-display-whole-numbers-as-percents/103969/4 "2025-03-20T18:43:10Z")

</div>

Related: [How to add ºC format in numeric entry field?](https://forum.inductiveautomation.com/t/how-to-add-c-format-in-numeric-entry-field/59705)

---

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [March 20, 2025, 6:49pm UTC](https://forum.inductiveautomation.com/t/how-to-get-numeric-entry-fields-to-display-whole-numbers-as-percents/103969/5 "2025-03-20T18:49:22Z")

</div>

It is _not_ possible on the "Numeric" entry field, because as you might expect, they are not intended to display string characters.

You could do it with a standard Text field, however it is considered poor practice.

1. It is confusing for the operator, are they intended to enter the units or not. If not, now you have to jump through hoops reacting to if the operator does enter the units, and you have to determine how the application will handle it.
2. It makes it harder to manage the units, what if you want to support both Imperial and SI units, or other units that are accepted for that value. You would be locked into what ever decision was made at design time. Using a label on the side makes it easier to support dynamic units or to change them at a later date.
3. It makes it harder to align the numbers in a way that looks professional (in this programmers opinion anyway). As where the units are aligned is dependent on how the text is displayed and other factors such as the actual value of the number.

Use the label on the side, you'll be better off for it in the long run.

---

<div class="post-metadata">

**Author:** ![Noah\_Gilgo](https://avatars.discourse-cdn.com/v4/letter/n/c89c15/32.png) [@Noah\_Gilgo](https://forum.inductiveautomation.com/u/Noah_Gilgo)\
**Post date:** [March 20, 2025, 7:41pm UTC](https://forum.inductiveautomation.com/t/how-to-get-numeric-entry-fields-to-display-whole-numbers-as-percents/103969/6 "2025-03-20T19:41:41Z")

</div>

Okay, this is what I'm going with. Thank you!
