# Numeric Text Field randomly does not update **URL:** \ **Category:** Ignition\ **Tags:** vision\ **Created:** [June 25, 2025, 12:29pm UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764 "2025-06-25T12:29:20Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [June 25, 2025, 12:29pm UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/1 "2025-06-25T12:29:20Z")
Vision 8.1.38 I have a standard template that contains a numeric text field, value linked to an OPC tag to Logix v34. On this template, operator can select entry, keyboard touchscreen entry, value entered, and OK selected. Randomly, the new value will appear in text field when the keypad closed, then within a second or two, revert back to the previous value. However the tag itself in the browser is the new value. On this template, the operator can press and a popup window appears that also has this numeric text entry on it. That window will show the correct new value, while the template numeric entry continues to show the previous value. On the entry field, defer updates is set to true, protected mode false, commit on focus true, and reject updates during edit true. Nothing external to this numeric text field is changing the value. Is there a setting im doing wrong? The last post in this thread mentioned something soecifically about templates, but I didnt understand it fully and whether applicable to my situation. > [@Text Field not updating after being selected](https://forum.inductiveautomation.com/t/text-field-not-updating-after-being-selected/24639/5): > > @PGriffith this is not the behavior I am looking for. “Commit on Focus Loss” just writes whatever is in the text field when the focus is lost on that text field. My issue is that when I have focus on a text field and within designer I do not edit the field but the tag value the field is showing changes, when the focus is lost on the text field the value never changes to the current tag value. It seems that when “Reject Updates During Edit” is true designer ignores the value change event that … ---
**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:** [June 25, 2025, 12:35pm UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/2 "2025-06-25T12:35:26Z")
This is a bidirectional binding? If not, it should be. ---
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [June 25, 2025, 12:39pm UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/3 "2025-06-25T12:39:18Z")
Yes. 95% of the time, it works. Every once in awhile, the above behaviour occurs. ![IMG_20250625_083947](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/5/75b6b00e3d266b1c60852c23444730b890f9bd47.jpeg) Both circled numeric text entries are linked to same tag. 425 is the updated value, 375 the old. ---
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [June 28, 2025, 2:05am UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/4 "2025-06-28T02:05:05Z")
Any ideas? ---
**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:** [June 28, 2025, 1:49pm UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/5 "2025-06-28T13:49:38Z")
> [@robertm](#): > > keyboard touchscreen entry, value entered, and OK selected. Is this the OS's or a custom popup? ---
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [June 28, 2025, 4:43pm UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/6 "2025-06-28T16:43:08Z")
OS's touchscreen keypad ---
**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:** [June 28, 2025, 9:58pm UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/7 "2025-06-28T21:58:19Z")
There's no destructive for this value in the PLC that could be creating a race condition? Beyond that, if the bidirectional binding can't be entirely trusted, I suppose switching to a write blocking script on the `floatValue` property change event would correct the issue. ---
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [June 28, 2025, 10:42pm UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/8 "2025-06-28T22:42:34Z")
No destructive. It's a read SP in code. It's odd it only seems to happen randomly when changed from the template. The popup works 100% of the time. ---
**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:** [June 29, 2025, 7:13am UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/9 "2025-06-29T07:13:16Z")
...so there are two numeric text fields bidirectionally bound to the same tag that are possibly open in the client simultaneously? I wonder if that's what's somehow triggering the racy behavior. It's probably worth reporting to support in case this is a bug on Ignition's side. ---
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [June 29, 2025, 8:54pm UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/10 "2025-06-29T20:54:43Z")
Somewhat. In the case of the template value, its not always when the popup is open. The most common scenario: Template SP is at 375 Select numeric text entry in template OS keypad presents Enter value of 425 Select OK Value in template briefly displays 425 but then reverts back to 375 Open popup that has same numeric entry binding Popup shows the correct 425 (This is the point screen image taken) Value in PLC and in tag browser is 425 But value in template numeric field persists at 375. Both template and popup are passed a pathstr and use indirect bindings. ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [June 30, 2025, 1:18am UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/11 "2025-06-30T01:18:19Z")
> [@robertm](#): > > Value in template briefly displays 425 but then reverts back to 375 what are your settings in the tag's Tag Group? what is the value in the PLC? ---
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [June 30, 2025, 5:10pm UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/12 "2025-06-30T17:10:49Z")
Value in PLC is 425, when template is displaying 375. Its on a slow poll group of 2000ms, so that might explain the behavior of it displaying the value entered in the keypad briefly in the numeric text entry before it reverts. The tag is part of a UDT looking at a CLX PID tag.SP, so maybe the driver isnt efficient at querying that, although it has always worked elsewhere. Attached is the template indirect value binding, the popup indirect binding, the UDT and the tag group. Only difference is I pass just the loop # to the template, whereas the full path to the popup, but its the same tag. ![20250630_125949](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/9/7976f2bf486fba31c5f7c12fd2edf602379a7d4e.jpeg) ![20250630_130201](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/9/f92c33dae00a5f94fd0e6e3a52b615f7448d9bfc.jpeg) ![20250630_130253](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/c/ec32c0f08fecc215e575b93938cc942904a5318f.jpeg) ![20250630_130332](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/2/32e1d5cba0b842bae4d3ca45c81a08adc74b656a.jpeg) ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [June 30, 2025, 10:21pm UTC](https://forum.inductiveautomation.com/t/numeric-text-field-randomly-does-not-update/107764/13 "2025-06-30T22:21:36Z")
Ok, I was half expecting to see read after write on which can cause this, but not so much in this instance. I'm not sure in this case.