# \[Bug-12999\]Perspective numeric entry does not obey format string **URL:** \ **Category:** Ignition Early Access\ **Created:** [March 6, 2019, 4:07am UTC](https://forum.inductiveautomation.com/t/bug-12999-perspective-numeric-entry-does-not-obey-format-string/23086 "2019-03-06T04:07:07Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ASF](https://avatars.discourse-cdn.com/v4/letter/a/c4cdca/32.png) [@ASF](https://forum.inductiveautomation.com/u/ASF)\ **Post date:** [March 6, 2019, 4:07am UTC](https://forum.inductiveautomation.com/t/bug-12999-perspective-numeric-entry-does-not-obey-format-string/23086/1 "2019-03-06T04:07:07Z")
Where a format string specifies at least one required decimal place, all optional decimal places are displayed even when they are not required. If all decimal places are optional, the format is displayed correctly. e.g. for the number 12.34 ```auto Format String >> Display 0.# >> 12.3 0.## >> 12.34 0.### >> 12.34 0.###### >> 12.34 0.0 >> 12.3 0.0# >> 12.34 0.0## >> 12.340 0.0##### >> 12.340000 ``` ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [March 6, 2019, 3:30pm UTC](https://forum.inductiveautomation.com/t/bug-12999-perspective-numeric-entry-does-not-obey-format-string/23086/2 "2019-03-06T15:30:43Z")
You’re right - that doesn’t look like what I would expect… I’ll open an internal ticket to get this fixed. ---
**Author:** ![jpark](https://avatars.discourse-cdn.com/v4/letter/j/a88e57/32.png) [@jpark](https://forum.inductiveautomation.com/u/jpark)\ **Post date:** [May 13, 2020, 1:50pm UTC](https://forum.inductiveautomation.com/t/bug-12999-perspective-numeric-entry-does-not-obey-format-string/23086/3 "2020-05-13T13:50:54Z")
Hello Ignition 8.0.13 nightly I have a numeric entry field displaying a decimal ( 123.456789 ) with a format of 0,0.## It display correctly as 123.46 but when you go to edit it display all decimal places. Should the format also apply when editing? Side note, is it possible to remove the up/down arrows on the numeric entry field when editing? ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [May 13, 2020, 3:33pm UTC](https://forum.inductiveautomation.com/t/bug-12999-perspective-numeric-entry-does-not-obey-format-string/23086/4 "2020-05-13T15:33:50Z")
It turns out that both of your questions regard expected behaviors. The format is only applied on a visual level so as not to change any value coming in (we don’t want to change values you supply - only how they’re visually represented). As for removing the arrows, Yousuf recommends using this: [https://www.w3schools.com/howto/howto\_css\_hide\_arrow\_number.asp](https://www.w3schools.com/howto/howto_css_hide_arrow_number.asp) Before the theming update we had removed them from Chrome but not Firefox. It sounds like going forward we’re going to be more hands-off since we’re allowing and encouraging customers to develop their own CSS. AS a result, we’ve removed the Chrome-specific removal of the arrows. ---
**Author:** ![Saad\_Ali\_Hassan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/saad_ali_hassan/32/52363_2.png) [@Saad\_Ali\_Hassan](https://forum.inductiveautomation.com/u/Saad_Ali_Hassan)\ **Post date:** [March 18, 2024, 12:15am UTC](https://forum.inductiveautomation.com/t/bug-12999-perspective-numeric-entry-does-not-obey-format-string/23086/5 "2024-03-18T00:15:34Z")
I am facing an issue where the customer wants to enter/display % but the backend requires a decimal value. Is there a simple solution to this using the input value component? This caught me attention as I could not find related topics to this. "The format is only applied on a visual level so as not to change any value coming in (we don’t want to change values you supply - only how they’re visually represented)." ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [March 18, 2024, 3:23pm UTC](https://forum.inductiveautomation.com/t/bug-12999-perspective-numeric-entry-does-not-obey-format-string/23086/6 "2024-03-18T15:23:54Z")
I'm sure you would find many here who would argue that `%` is akin to units, and should be handled externally of the input. It is not common to specify units within an input, but it is common to specify the units in some sort of associated label: "pallet weight (in kg)". Percent should be used the same way: "Progress (as a percent)". ![Screenshot 2024-03-18 at 8.23.42 AM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/5/853064494d3da28d0e4990269203967ee453d6f4.png) If you're using `NumericEntryField.props.format`, then the user doesn't supply the `%` piece - just the number. A value of `.23` supplied by the user will be formatted and then rendered as `23%` ![Screenshot 2024-03-18 at 8.27.26 AM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/9/e9587795247fc79c87072928ff8f73f78e2815f7.png) ---
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [September 28, 2024, 4:23pm UTC](https://forum.inductiveautomation.com/t/bug-12999-perspective-numeric-entry-does-not-obey-format-string/23086/7 "2024-09-28T16:23:50Z")
With a float value and a format like 0.000, the value displayed is ok but when the user edit the value, the value is displayed with all the digit and it's error prone. IMHO it will be much more suitable to display the formatted value (0,007 in my case). Each time the user need to navigate in a tiny edit box and suppress all digit to input the new value. An option to apply the format during input would be perfect ! ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/a/ca6939b61c717bca4746da5954e79e8042e889bd.png)