# How to force numeric keyboard instead of qwerty on IOS?

**URL:** <https://forum.inductiveautomation.com/t/how-to-force-numeric-keyboard-instead-of-qwerty-on-ios/110584>\
**Category:** Ignition\
**Created:** [September 12, 2025, 3:40pm UTC](https://forum.inductiveautomation.com/t/how-to-force-numeric-keyboard-instead-of-qwerty-on-ios/110584 "2025-09-12T15:40:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hw79](https://avatars.discourse-cdn.com/v4/letter/h/838e76/32.png) [@hw79](https://forum.inductiveautomation.com/u/hw79)\
**Post date:** [September 12, 2025, 3:40pm UTC](https://forum.inductiveautomation.com/t/how-to-force-numeric-keyboard-instead-of-qwerty-on-ios/110584/1 "2025-09-12T15:40:16Z")

</div>

Is there a way to force the ios keyboard into the numeric mode when a user gives focus to a text entry field?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [September 12, 2025, 3:44pm UTC](https://forum.inductiveautomation.com/t/how-to-force-numeric-keyboard-instead-of-qwerty-on-ios/110584/2 "2025-09-12T15:44:24Z")

</div>

Not at present, ~~though as far as I know the new Form component in 8.3 has modes that hint to the underlying OS appropriately to show the 'correct' keyboard.~~ a quick look at the manual suggests this hasn't (yet?) landed

---

<div class="post-metadata">

**Author:** ![colby-noah](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby-noah/32/87508_2.png) [@colby-noah](https://forum.inductiveautomation.com/u/colby-noah)\
**Post date:** [September 12, 2025, 6:42pm UTC](https://forum.inductiveautomation.com/t/how-to-force-numeric-keyboard-instead-of-qwerty-on-ios/110584/3 "2025-09-12T18:42:28Z")

</div>

It’s possible to do this but the method is a bit hacky, and I haven’t looked into it enough to see if there are any big drawbacks.

You can create a Markdown component with `escapeHtml: false` and `source: <input type=”tel”>`, then give it an event script for `onKeyDown` that looks something like this:

```python
def runAction(self, event):
	if event.keyCode == 8:
		self.view.custom.numbers = self.view.custom.numbers[:-1]
	elif event.keyCode in range(48, 58):
		self.view.custom.numbers += event.key

```

In this example I’m writing to a custom property I made to store the input, since input with the Markdown component is weird (and probably not intended to be a thing). You would have to tweak this to work better with your constraints and be sure to sanitize the input.

Honestly, I would probably recommend against doing this, but I thought it would be fun to share.