Power Platform Community Forum Thread Details

Good morning,

Believe I've discovered a (reproducible) bug with the Modern Number Input control.

TL;DR - when it's in DisplayMode.View, the control displays the last non-null value it held despite its value being updated to a null value.

Replication instructions:

In a canvas app, add two modern number input controls.
Set one of them to DisplayMode.View, leave the other on the default (Enabled)
Add a button to update a context variable to some number (can use anything)
Add another button to update the context variable to a different number
Add a final button to update the context variable to null - set to Blank()
Click around on the buttons and observe the difference in behavior when going from any value to the null value, as opposed to going from any value to any other value.

Expected behavior:

Both number inputs should follow the value of the context variable regardless of what display mode they are in

Actual behavior:

The input in Edit mode behaves as expected.
The input in View mode will not clear when its value changes to null, instead, it still displays the last value it held.
Accessing the value property from outside the control works as expected, i.e. it shows a null value

Screenshots:

All controls respond as normal when their value is updated to a 'real' value (one that isn't Blank)

The modern number input specifically does not clear its display when the value is updated to Blank. Notice that accessing the Value property of the control from outside does return blank as expected.

Categories:

Experimental features

This looks like a bug in the Modern Number Input control's behavior when set to DisplayMode.View. The control seems to retain the last non-null value in its UI display even though its Value property correctly updates to Blank().

✅ Workarounds to Fix the Display Issue

Since this appears to be a UI issue (not a data issue), here are a few workarounds you can try:

1️⃣ Force a Refresh by Binding to a Label

Instead of directly setting the control’s value, force a UI refresh using an intermediary label:

Add a hidden label (lblRefresh) and set its Text property to:

If(IsBlank(varNumber), "", varNumber)
Then, set the Modern Number Input's Default property to:

Value(lblRefresh.Text)

🔹 Why?

The label will always return an empty string ("") when varNumber is Blank(), forcing the UI to update.
Since the number input correctly handles non-blank values, this will keep its behavior consistent.

2️⃣ Use a Conditional DisplayMode Toggle

Instead of directly setting the number input to DisplayMode.View, toggle its mode based on whether the value is blank:

🔹 Why?

DisplayMode.Disabled forces the UI to refresh while keeping the field read-only.
When varNumber is not blank, it switches back to DisplayMode.View.

3️⃣ Alternative: Use an Editable Number Input Instead

If using DisplayMode.View is not strictly necessary, try keeping the control in Edit mode and use DisplayMode.Disabled instead. It will correctly show a blank value when the variable is Blank().

🔍 Reporting to Microsoft

If you're confident this is a reproducible bug, consider reporting it:

Microsoft Power Apps Community Forum: Power Apps Community
Microsoft Support: Submit a ticket

Final Thoughts

This is likely an issue with how DisplayMode.View caches and retains values.
The workarounds ensure the UI reflects the blank value properly.
If Microsoft fixes this, the workarounds won’t be needed anymore.