Number input modern control ( BUG )

(2) Share

Report

Posted on by CU07031518-0

Hi,

I'm using the modern number input within a form, when enter the new value and press a button to submit the form the previous value entered into the control is recorded and not the new value, and this issue is very frustrating.

In modern number input control missing the TriggerOutput property that allows updating the entered value without leaving the field.

The TriggerOutput property is present in the modern text input but not in the modern number input, this makes the modern number input control unusable.

Has anyone else encountered this problem with number input control ?

Thanks and best regards.

Categories:

Power Apps Pro Dev & ISV

I have the same question (5)

All responses (12)

Answers (0)

ronaldwalcott 3,847 Super User 2025 Season 2 on at

Like (0)

Report

Never seen that happen. Are you using patch or submit?

Was this reply helpful? Yes No
CU07031518-0 18 on at

Like (0)

Report

I use form and a button with SubmitForm function.

If edit a existing sharepoint item with number field through number input control, for example with the value 7, I change the value to 8 and press the submit button, 7 is saved again because the inputnumber.Value property still contains the previous value and not the new value 8 !

I noticed instead that if I change the value to 8 and click outside the input number control and then save then the new value is recorded correctly.

It seems that if you stay focused on the input number control - change the value - and then submit the form with the button, the new value is not updated correctly.

I hope I explained myself.

Thanks

Was this reply helpful? Yes No
Ravi-Prajapati 416 Super User 2025 Season 2 on at

Like (1)

Report
Yes, this is a known issue with the Modern Number Input control in Power Apps, where it does not update the value immediately upon entry, causing the form to submit the previous value instead of the new one. This happens because the TriggerOutput property (which forces an update) is missing in the modern number input.

✅ Workarounds to Fix the Issue

1️⃣ Force Update the Control with OnChange

Since the number input does not update automatically, you can use the OnChange property to manually update a variable and bind it to the control.

Steps:

Set the Default property of the number input to a variable:

In the OnChange property of the Number Input, update the variable:

Set(varNumberInput, ModernNumberInputControl.Value)

Now, the form will store the latest value when submitted.

2️⃣ Use a Hidden Modern Text Input to Capture the Value

Since Modern Text Input has TriggerOutput, you can link it to the number input to force an update.

Steps:

Insert a Hidden Modern Text Input (set Visible to false).

Set its Default property to the Modern Number Input control’s value:

ModernNumberInputControl.Value

Now, use this hidden text input as the value source in your form.

3️⃣ Use a Classic Number Input Instead of Modern

If the above workarounds do not provide the desired behavior, consider switching back to the classic Number Input control, which does not have this issue.

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

CU07031518-0 18 on at

Like (1)

Report

ok, thanks for your workarounds.

I hope microsoft to fix the issue by adding the TriggerOutput property to modern number input otherwise the control is unusable.

what do you say @CU04021533-0 ?

Was this reply helpful? Yes No
CarlosFigueira on at

Like (0)

Report

Thank you for reporting this issue, I can reproduce it internally. I notified the product team, and they are working on a fix. As a work around, you can replace the number input in the form with a text input control, and set the TriggerOutput to either Delayed or Key Press.

Was this reply helpful? Yes No
CU07031518-0 18 on at

Like (0)

Report

Hi,

Are there any updates on this problem?

I don't think it's a problem to be underestimated given that since it updates the previous value in the case of submitting the form with control

I'm wondering a couple of things about this:

1 - whether the modern number input is actually used by anyone since no one reports this issue in the community

2 - if this bug is known and therefore no one or few use modern number input control in canvas applications

3 - When does Microsoft plan to fix this bug?

Thanks

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

MarsOne 4 on at

Like (0)

Report

-

Was this reply helpful? Yes No
NConley9 3 on at

Like (0)

Report

I am experiencing this as well. Can cofirm that suggested workaround #2 does not work. You need to use the modern text input in place of the number input. If you use it hidden, it will not update as the number input still will report the old value.

Was this reply helpful? Yes No
CU07031518-0 18 on at

Like (0)

Report

I also confirm that suggested workaround #1 and #2 does not work, at this point all that remains is to use the classic text input with number format property.

When does microsoft plan to fix this BUG?

Was this reply helpful? Yes No
Mofi 2 on at

Like (0)

Report

I tried multiple things, I ended up replacing Numer Input (Modern) with TextInput (Classic)

Code for a formated classic text input allowing numbers to look as closed as modern Number Imput to keep a modern form consistent

- DataCardValue35:
Control: Classic/TextInput@2.3.2
Properties:
BorderColor: =If(IsBlank(Parent.Error), Color.Transparent,RGBA(200, 50, 50, 1))
BorderThickness: =1
Default: =Parent.Default
DelayOutput: =true
DisplayMode: =Parent.DisplayMode
Fill: =RGBA(242, 243, 244, 1)
FocusedBorderColor: =App.Theme.Colors.Darker40
FocusedBorderThickness: =1
Format: =TextFormat.Number
Height: =30
HoverBorderColor: =
HoverColor: =
HoverFill: =
PaddingLeft: =10
PressedBorderColor: =
PressedColor: |
=
PressedFill: =
RadiusBottomLeft: =0
RadiusBottomRight: =0
RadiusTopLeft: =0
RadiusTopRight: =0
Size: =10
Tooltip: =Parent.DisplayName
Width: =Parent.Width - 48
X: =24
Y: =DataCardKey35.Y + DataCardKey35.Height + 4

2 people found this reply helpful.

Was this reply helpful? Yes No