# Vision numeric text field component decimal format not respected on keypad **URL:** \ **Category:** Ignition\ **Tags:** vision, ignition81\ **Created:** [May 16, 2025, 3:10pm UTC](https://forum.inductiveautomation.com/t/vision-numeric-text-field-component-decimal-format-not-respected-on-keypad/106335 "2025-05-16T15:10:41Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\ **Post date:** [May 16, 2025, 3:10pm UTC](https://forum.inductiveautomation.com/t/vision-numeric-text-field-component-decimal-format-not-respected-on-keypad/106335/1 "2025-05-16T15:10:41Z")
Using vision on 8.1.44. We have a touch screen running vision. There's a numeric text field that we allow a large integer to be input into, and on the decimal format field we have a `0` which removes the commas so it looks like ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/a/6aa82d722a4389e75b7dc0572ec86298a8a7aeaf.png) However when the operator presses the text field to change the number, the on screen keyboard looks like ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/3/03b512dce3bb761ebed27cce6571f98a393a31f0.png) So there's a minor mismatch between what they enter (with a comma) and how it looks in the numeric text field component. Anyone find a way to make they keyboard number formatting match the component? Or to just make it comma-less in general? ---
**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\ **Post date:** [May 23, 2025, 6:23am UTC](https://forum.inductiveautomation.com/t/vision-numeric-text-field-component-decimal-format-not-respected-on-keypad/106335/2 "2025-05-23T06:23:52Z")
This is an OS generated keyboard? If so, which OS? ---
**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\ **Post date:** [May 23, 2025, 1:32pm UTC](https://forum.inductiveautomation.com/t/vision-numeric-text-field-component-decimal-format-not-respected-on-keypad/106335/3 "2025-05-23T13:32:32Z")
It may have been. It was a touch screen panel (model unknown to me atm), touchscreen mode enabled in project properties. Believe it was a windows 10. Implication being this would need to be changed on the OS level though? ---
**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\ **Post date:** [May 24, 2025, 1:47am UTC](https://forum.inductiveautomation.com/t/vision-numeric-text-field-component-decimal-format-not-respected-on-keypad/106335/4 "2025-05-24T01:47:11Z")
> [@bkarabinchak.psi](#): > > this would need to be changed on the OS level though? That's my guess. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [May 24, 2025, 4:39am UTC](https://forum.inductiveautomation.com/t/vision-numeric-text-field-component-decimal-format-not-respected-on-keypad/106335/5 "2025-05-24T04:39:37Z")
This is the Vision keypad, not the OS keypad I honestly don't know though if there's a way.