# Datetime Typed Input

**URL:** <https://forum.inductiveautomation.com/t/datetime-typed-input/114177>\
**Category:** Ignition\
**Tags:** perspective, ignition81\
**Created:** [February 25, 2026, 5:20pm UTC](https://forum.inductiveautomation.com/t/datetime-typed-input/114177 "2026-02-25T17:20:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robert\_McIlvenna](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/robert_mcilvenna/32/80238_2.png) [@Robert\_McIlvenna](https://forum.inductiveautomation.com/u/Robert_McIlvenna)\
**Post date:** [February 25, 2026, 5:20pm UTC](https://forum.inductiveautomation.com/t/datetime-typed-input/114177/1 "2026-02-25T17:20:32Z")

</div>

Is there something similar to FormattedTextField in Perspective?

Especially for dates, clicking 50 times to get to a specific month, year, day, hours and minute is quite annoying and takes longer than just having a specific format muscle memoried. DatetimeInput has a caret in its icon, but as far as I am able to tell, I can’t type into it?

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/7/27c27bbc84ffd38aa6200485a07496e20c6b830f.png)

I’ve read through the docs and forums and no matter what I do I am forced to use the popup picker? I want to be able to type, and it adds in the dashes, slashes, and spaces. eg. 2026010210000000 becomes 2026-01-02 10:00:00. Am I missing something?

---

<div class="post-metadata">

**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\
**Post date:** [February 25, 2026, 5:29pm UTC](https://forum.inductiveautomation.com/t/datetime-typed-input/114177/2 "2026-02-25T17:29:55Z")

</div>

This was an idea for entering IP address, but you might be able to tweak to your use case. I would have an additional confirm button so whatever is tied to the value doesn't thrash while you are entering a value. If you built it in a custom popup then you could send new value on popup close.

> [@IP address data entry / validation ideas?](https://forum.inductiveautomation.com/t/ip-address-data-entry-validation-ideas/106538/7):
>
> On a more serious note, text field, deferUpdates and rejectUpdatesWhileFocused off. Value change event that fires on browser source only, that applies regex filter to entered value and strips unallowed items (\D if using java regex) or enters the max/min value if going beyond edges and writes it back to a custom property on the view. The numeric entry is bound unidirectionally to this custom property. I think you could also use this script to send focus to the next box on 3rd digit entry. Migh…

I don't think there is anything built in. If you have the resources, a custom module that adds a component specifically for this might be reasonable.

---

<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:** [February 25, 2026, 5:35pm UTC](https://forum.inductiveautomation.com/t/datetime-typed-input/114177/3 "2026-02-25T17:35:19Z")

</div>

In 8.3, the new Form component gives you access to a wide variety of client side validation options:

> **[Widget Validation​ - Perspective - Form | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/appendix/components/perspective-components/perspective-input-palette/perspective-form#widget-validation)**
>
> 💡Have feedback for this page? Let us know on the IA Forum. | The Form component is used to create responsive and dynamic forms for user input and validation in Perspective.

---

<div class="post-metadata">

**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\
**Post date:** [February 25, 2026, 5:41pm UTC](https://forum.inductiveautomation.com/t/datetime-typed-input/114177/4 "2026-02-25T17:41:58Z")

</div>

How difficult would it be to bring these validation options over to the regular perspective text field? (And possibly backported to 8.1?)

I guess having the form available eliminates the need for the validation on the regular text entry field?

---

<div class="post-metadata">

**Author:** ![Robert\_McIlvenna](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/robert_mcilvenna/32/80238_2.png) [@Robert\_McIlvenna](https://forum.inductiveautomation.com/u/Robert_McIlvenna)\
**Post date:** [February 25, 2026, 5:44pm UTC](https://forum.inductiveautomation.com/t/datetime-typed-input/114177/5 "2026-02-25T17:44:55Z")

</div>

Validation is one thing, what I mean is more convenience. Like when you type in a phone number or credit card, even dates ive seen do this, and it just adds in the extra stuff for you _as you type_. I’ve tried doing this a bit with the text field, but it was always kind of a pain. I might be able to do it with an underlying textfield that focuses itself and is invisible. I havent found a satisfactory solution to this, this might be a good foray into perspective component module dev though

---

<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:** [February 26, 2026, 4:41pm UTC](https://forum.inductiveautomation.com/t/datetime-typed-input/114177/6 "2026-02-26T16:41:12Z")

</div>

The validation and behavior in the form component is basically what's available on the `input` element: [\<input\>: The HTML Input element - HTML | MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input)

A lot of the behavior you get "for free" from the user agent (browser), which gives you better performance and native "feeling" controls (e.g. a specialized popup keyboard on mobile devices for email/telephone entries), vs creating fully custom behaviors that rely on Javascript we bundle and deliver on the page.

That said, it definitely would be _possible_ to create custom components that have some of those niceties.
