Skip to main content
4-Participant
September 8, 2026
Solved

Mashup NumericInputMode on ptcstextfield transposes number when Entering Decimals

  • September 8, 2026
  • 4 replies
  • 74 views

I have a mashup that contains a ptcstextfield widget.  NumericInputMode is selected.  Allow decimals is selected.  DecimalPlaces is set  to 2.  When I attempt to enter a decimal value, it transposes the numbers.  If I enter .75, it shows the value as .57.  Any ideas on what might be causing this issue.

Best answer by Nathaniel_S

Hello ​@SB_12787070, I have confirmed with R&D that this issue is known and has been fixed in ThingWorx version 10.1.2 (and 10.2.0). Please use the proposed workaround (type the leading zero) until you are able to upgrade to the fix version.

4 replies

Community Manager
September 10, 2026

Hello ​@SB_12787070 

Could you please let us know what version of ThingWorx you are using? I have attempted to recreate what you observed in both 9.5 and 10.0 but neither version has a NumericInputMode parameter. Also, is this occurring in multiple browsers (i.e. chrome and firefox)? Does the issue occur when a delay is given between inputting digits? If the value is output, say to a value display or Thing property, does it show the transposed number as well?
If you could provide steps to recreate the issue, preferably with screen captures, that would help the community in understanding how you are running into this problem.

Best regards, Nathaniel
4-Participant
September 15, 2026

I’m using Thingworx 10.1. It is occurring in Edge and Chrome browsers. Screen Shots are Attached. 

Community Manager
September 21, 2026

Got it, those options only appear in 10.1 and not in prior versions. I am able to replicate the behavior you are seeing only when inputting a decimal without a leading number (i.e. “.75” as opposed to “0.75”). If a leading zero isn’t used the widget automatically places one there after the first digit is input and resets the cursor to just behind the decimal (using a pipe for the cursor, “.7|” is changed to “0.|7”). Using a leading zero when entering decimal values seems to prevent the behavior, and should be used as a workaround for now.

Best regards, Nathaniel
Community Manager
September 24, 2026

Hello ​@SB_12787070, I have confirmed with R&D that this issue is known and has been fixed in ThingWorx version 10.1.2 (and 10.2.0). Please use the proposed workaround (type the leading zero) until you are able to upgrade to the fix version.

Best regards, Nathaniel